Acknowledgements
AllySec Forge stands on the shoulders of open-source projects, security research communities, and the operators who shared their knowledge. We acknowledge the specific contributions that shaped our architecture and capabilities.
Agent Framework & Architecture
| Project | License | Contribution |
|---|---|---|
| Claude Code | — | Agent loop architecture, tool-use protocol, and multi-turn execution patterns. We reimplemented all execution layers with our own Python bridge and Kali-native tooling, but the foundational agent-loop concept (screenshot → analysis → action, forked subagents, memory consolidation) traces to this lineage. |
| OpenCode | MIT | Model routing and credential pooling strategies. Our provider discovery system and multi-model fallback logic were informed by their approach to AI provider abstraction. |
Memory System
| Project | License | Contribution |
|---|---|---|
| Hermes Agents Memory | MIT | Persistent memory taxonomy (user/feedback/project/reference types) and the MEMORY.md index pattern. Our AutoDream consolidation mechanism and cross-session persistence build on these concepts, adapted for security engagement workflows. |
Tool Integration & Skill Architecture
| Project | License | Contribution |
|---|---|---|
| CommunityTools | CC0 | Skill-suite organization pattern and the script-to-skill mapping taxonomy. Our 24 skill suites and 147 Python attack scripts follow this classification philosophy, specialized for autonomous agent execution. |
Computer Use & Vision
| Project | License | Contribution |
|---|---|---|
| wimi321/macos-computer-use-skill | MIT | Python bridge architecture replacing native Swift modules. The mac_helper.py runtime approach and executor.ts adapter pattern directly enabled our macOS Computer Use capability without private dependencies. |
| domdomegg/computer-use-mcp | MIT | Cross-platform Computer Use MCP server design reference. Provided the standalone MCP server architecture that influenced our tool dispatch layer. |
Documentation & Site Design
| Project | License | Contribution |
|---|---|---|
| VitePress | MIT | Documentation site framework and static site generation. |
| docsify | MIT | Documentation navigation patterns and sidebar organization (Atlas docs lineage). |
Kali Linux Ecosystem
| Project | License | Contribution |
|---|---|---|
| Kali Linux | Various | The 2,400+ tool catalog and container infrastructure. Our Docker-native Kali integration and 262 mapped tools across 7 pentest phases are built on this foundation. |
| Exploit-DB | Public | Verified exploit signatures and PoC references that inform our ExploitTool validation. |
Security Research Communities
| Community | Contribution |
|---|---|
| OWASP | Web vulnerability taxonomy (SQLi, XSS, IDOR, SSRF, SSTI) that structures our webapp-exploit-hunter suite. |
| MITRE ATT&CK | Tactics and techniques framework referenced in our attack chain scoring and impact assessment. |
| HackerOne | Disclosure methodology and scope-driven testing patterns that inform our bug bounty orchestration. |
What We Rebuilt
Every acknowledgment above is for architectural inspiration or interface patterns. The following components were written entirely by AllySecLabs:
- Operator Agent engine — custom forked-agent orchestration, worktree isolation, and engagement state machine
- KaliTool adapter — Docker container discovery, auto-deploy, and 2,400+ command routing
- ExploitTool framework — 13 exploit types with autonomous PoC generation
- AttackChainTool — Multi-step exploit chain composer with impact scoring
- AutoDream — LLM-driven memory consolidation with conflict resolution and stale detection
- C2AdaptixTool — Adaptix C2 integration and Discord fallback infrastructure
The Allied Operators
Beyond code, AllySec Forge is shaped by the operators who shared their engagement workflows, tool preferences, and the hard lessons learned from real targets. The Forge is built by the allies, for the operators.
If you believe a project or community should be listed here, please open an issue or pull request.