# Decepticon

> Autonomous Hacking Agent

## Docs

- [Agents](https://docs.decepticon.red/en/architecture/agents.md): Seventeen specialist agents organized by engagement phase, each with dedicated tools, skills, and a clean context window.
- [Infrastructure](https://docs.decepticon.red/en/architecture/infrastructure.md): Two isolated Docker networks, complete separation between management and operations.
- [Middleware Stack](https://docs.decepticon.red/en/architecture/middleware-stack.md): Cross-cutting concerns — RoE enforcement, skills, OPPLAN, caching — applied uniformly across every Decepticon agent.
- [CLI Reference](https://docs.decepticon.red/en/cli-reference.md): Complete reference for all Decepticon CLI commands and options.
- [MITRE ATT&CK](https://docs.decepticon.red/en/concepts/mitre-attack.md): Tactics, Techniques, Procedures — the shared vocabulary between real threats, Decepticon, and the blue team.
- [Red Team Engagement Lifecycle](https://docs.decepticon.red/en/concepts/red-team-lifecycle.md): Get In, Stay In, Act — the three-phase lifecycle and how Decepticon executes each phase autonomously.
- [Roles & Cells](https://docs.decepticon.red/en/concepts/roles-and-cells.md): Red Cell, Blue Cell, White Cell, Trusted Agent — and where Decepticon fits in the engagement structure.
- [Threat Emulation](https://docs.decepticon.red/en/concepts/threat-emulation.md): Threat Gets a Vote — how Decepticon turns a threat profile into an executable engagement.
- [Tradecraft & OPSEC](https://docs.decepticon.red/en/concepts/tradecraft.md): DO and DON'T principles for autonomous red team operation — codified into Decepticon's middleware.
- [Contributing Guide](https://docs.decepticon.red/en/contributing/contributing-guide.md): How to contribute to Decepticon — code, skills, documentation, and community.
- [Developer Setup](https://docs.decepticon.red/en/contributing/developer-setup.md): Set up your local development environment for contributing to Decepticon.
- [Autonomous Execution](https://docs.decepticon.red/en/features/autonomous-execution.md): How Decepticon orchestrates multi-stage kill chains with fresh context per objective.
- [Benchmark & Evaluation](https://docs.decepticon.red/en/features/benchmark-evaluation.md): How Decepticon is measured against CTF-style challenges and validation benchmarks.
- [C2 Integration](https://docs.decepticon.red/en/features/c2-integration.md): Sliver C2 team server integration for implant deployment, session management, and post-exploitation.
- [Engagement Planning](https://docs.decepticon.red/en/features/engagement-planning.md): How Soundwave generates complete Red Team engagement documentation — RoE, ConOps, OPPLAN.
- [Knowledge Graph](https://docs.decepticon.red/en/features/knowledge-graph.md): The Neo4j-backed attack graph that turns ephemeral findings into a queryable engagement record.
- [Multi-Model Routing](https://docs.decepticon.red/en/features/multi-model-routing.md): LiteLLM-powered model routing with role-based profiles and automatic fallback.
- [Offensive Vaccine Pipeline](https://docs.decepticon.red/en/features/offensive-vaccine-pipeline.md): The five-stage vulnerability research pipeline — Scanner, Detector, Verifier, Exploiter, Patcher — that turns an attack into a defense.
- [OPPLAN System](https://docs.decepticon.red/en/features/opplan-system.md): The structured operations plan that turns a threat profile into an executable agent workflow.
- [Skill System](https://docs.decepticon.red/en/features/skill-system.md): Progressive skill disclosure with MITRE ATT&CK mapping across the kill chain.
- [Configuration](https://docs.decepticon.red/en/getting-started/configuration.md): Configure API keys, model profiles, and environment settings for Decepticon.
- [Quick Start](https://docs.decepticon.red/en/getting-started/quick-start.md): Install Decepticon and run your first autonomous Red Team operation in minutes.
- [History & Evolution](https://docs.decepticon.red/en/introduction/history-and-evolution.md): The architectural journey of Decepticon: from Purple Team AI to Autonomous Hacking.
- [Overview](https://docs.decepticon.red/en/introduction/overview.md): Autonomous Hacking Agent, Decepticon
- [Pentesting vs Red Teaming](https://docs.decepticon.red/en/introduction/pentesting-vs-redteaming.md): Why Decepticon is a Red Team Agent, not a vulnerability scanner — and how Autonomous Red Teaming extends the discipline.
- [Autonomous Hacking](https://docs.decepticon.red/en/vision/autonomous-hacking.md): What Autonomous Hacking means, why it replaces 'Vibe Hacking', and how it connects offense to defense.
- [Core Philosophy](https://docs.decepticon.red/en/vision/core-philosophy.md): The foundational principles that drive Decepticon's design as a Autonomous Hacking Agent.
- [Target Architecture](https://docs.decepticon.red/en/vision/target-architecture.md): Where Decepticon is headed: the architectural vision for the major refactoring.
- [Why Open Source?](https://docs.decepticon.red/en/vision/why-open-source.md): Decepticon's open source model goes beyond code—it's about building collective intelligence for the security ecosystem.

## OpenAPI Specs

- [openapi](https://docs.decepticon.red/api-reference/openapi.json)