Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.decepticon.red/llms.txt

Use this file to discover all available pages before exploring further.

​
API Key Setup

Decepticon requires an LLM API key to power its agents. Run the interactive setup wizard: 
decepticon onboard          # Primary setup flow
decepticon onboard --reset  # Reconfigure from scratch

​
Supported Providers

Decepticon uses LiteLLM as its model proxy, supporting any compatible backend:
ProviderModelsNotes
Anthropic APIClaude Opus, Sonnet, HaikuRecommended for best performance
Anthropic OAuthSame models, via Claude subscriptionUse Claude Code OAuth credentials
OpenAIGPT-5.5, GPT-5.4, GPT-5-nanoFull support with automatic fallback
GoogleGemini 2.5 Pro / Flash / Flash-LiteVia LiteLLM proxy
MiniMaxMiniMax-M2.5, MiniMax-M2.5-lightningAlternative high/mid tier
CustomAny LiteLLM backendSelf-hosted or alternative providers

​
Environment Variables

You can also configure via environment variables: 
# Primary provider
export ANTHROPIC_API_KEY="sk-ant-..."

# Or OpenAI
export OPENAI_API_KEY="sk-..."

# Or set via LiteLLM config for custom backends

​
Model Profiles

Decepticon routes different agent roles to different model tiers for optimal cost/performance balance:
ProfileOrchestratorExploitReconUse Case
ecoOpus 4.7Sonnet 4.6Haiku 4.5Production — best cost/performance ratio (default)
maxOpus 4.7Opus 4.7Sonnet 4.6High-value targets — maximum capability
testHaiku 4.5Haiku 4.5Haiku 4.5Development/CI — fast iteration
Each profile includes automatic fallback chains. If the primary provider is unavailable or rate-limited, Decepticon seamlessly switches to the next provider in the chain (e.g., Opus 4.7 → GPT-5.5 → Gemini 2.5 Pro → MiniMax-M2.5).
Select your profile during decepticon onboard or set it at any time via the DECEPTICON_MODEL_PROFILE environment variable. The eco profile is the default and recommended for most operations.

​
C2 Configuration

Sliver C2 integration is profile-based via Docker Compose. The COMPOSE_PROFILES environment variable is read from your .env (or shell) before the launcher starts the stack — it is not a flag to the decepticon command itself. Sliver is enabled by default. 
# .env (default)
COMPOSE_PROFILES=c2-sliver

# Or override per-run via shell
COMPOSE_PROFILES=c2-sliver decepticon
When enabled, the Sliver team server starts on the operational network with:
  • Auto-generated operator configuration
  • Pre-installed sliver-client in the sandbox
  • mTLS, HTTPS, and DNS C2 channel support

C2 Integration

Learn more about Sliver C2 integration and C2 channel configuration.

​
Docker Resources

Decepticon runs entirely in Docker containers. Recommended resource allocation:
ComponentCPUMemoryNotes
LangGraph Platform1 core1 GBManagement network — agent orchestration
LiteLLM Proxy0.5 core512 MBManagement network
PostgreSQL0.5 core512 MBManagement network — engagement state
Neo4j1 core1 GBBridges both networks — knowledge graph
Web Dashboard0.5 core512 MBManagement network — Next.js
Kali Sandbox2 cores4 GBOperational network — runs offensive tools
Sliver C21 core1 GBOperational network (default profile)
The Kali sandbox requires the most resources as it runs the full offensive toolkit. Allocate at least 4 GB of memory for stable operation during complex engagements.