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.

​
We Welcome Contributions

Whether you’re a security researcher, an AI engineer, or someone who cares about making defense better — there’s a place for you here.

​
Ways to Contribute

Code

Agent improvements, tool integrations, infrastructure enhancements, bug fixes, and test coverage.

Skills

New offensive techniques for the skill library — tagged with MITRE ATT&CK IDs and organized by kill chain phase.

Documentation

Improve these docs, write tutorials, add examples, or translate to new languages.

Community

Answer questions on Discord, share engagement patterns, report bugs, or discuss new features.

​
Contribution Workflow

1

Fork the Repository

Fork PurpleAILAB/Decepticon to your GitHub account.
2

Create a Feature Branch

Branch from main with a descriptive name:
git checkout -b feature/add-kerberoasting-skill
3

Develop

Make your changes using the Developer Setup. Run tests:
make test
make lint
4

Commit with Conventional Commits

Decepticon follows the Conventional Commits format: type(scope): subject. Common types: feat, fix, docs, refactor, test, chore. Write the body to explain the why, not just the what.
feat(agents): add Cloud Hunter skill for AWS metadata abuse
fix(opplan): resolve dependency cycle in objective_expand
docs(features): document the offensive vaccine pipeline
5

Open a Pull Request

Push your branch and open a PR against main. Describe what your change does and why.

​
Skill Contributions

Adding new skills to the library is one of the most valuable contributions. Each skill should include:
  • Frontmatter — Name, description, MITRE ATT&CK technique IDs, kill chain phase, required tools
  • Content — Step-by-step technique execution, command examples, expected output
  • Detection Notes — How defenders can detect this technique (feeds the defensive evolution vision)
  • Prerequisites — What access or conditions are needed

​
Code Style

  • Follow the existing patterns in the codebase
  • Run make lint before submitting
  • Include tests for new functionality
  • Document non-obvious design decisions in comments

​
Community

Discord

Ask questions, share techniques, connect with the team.

GitHub Issues

Report bugs, request features, track roadmap.

GitHub Discussions

Longer-form conversations about architecture, strategy, and ideas.

​
License

Decepticon is licensed under Apache-2.0. By contributing, you agree that your contributions will be licensed under the same terms.