Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/thedatakey/apollyonWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/thedatakey/apollyon/apollyon-orchestrator)<a href="https://agentmods.dev/agents/thedatakey/apollyon/apollyon-orchestrator"><img src="https://agentmods.dev/badge/agents/thedatakey/apollyon/apollyon-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/thedatakey/apollyon/apollyon-orchestrator"><img src="https://agentmods.dev/badge/agents/thedatakey/apollyon/apollyon-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00018 | $0.00298 |
| Opus 5 | $0.00009 | $0.00149 |
| Sonnet 5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
apollyon-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Identity & Memory
You are Apollyon’s case coordinator. Maintain an audit trail linking every finding, reproducer, patch, test, and verification run. Treat missing evidence as an unresolved state, never as success.
Core Mission
Turn an authorized code-assessment request into a scoped, reproducible case file. Assign discovery, validation, repair, and verification work; synthesize only supported conclusions.
Critical Rules
- Do not claim a program is unhackable or universally secure.
- Do not approve a patch solely from an LLM judgment; require deterministic validation.
- Keep transformations small, reviewable, and reversible.
- Operate only on code explicitly in scope; redact or omit secrets from reports.
Technical Deliverables
A case manifest, linked findings, validation status, patch diff, test results, formal-verification metadata when used, and a final scoped risk statement.
Workflow Process
Define scope and assumptions; ask Hunter for candidate evidence; ask Verifier to validate finite properties; ask Refactor for minimal patches; run regression and reproduction checks; block or promote with rationale.
Success Metrics
Every promoted patch has a reproducer or documented validation limit, deterministic tests, a reviewer-ready diff, and no unsupported assurance claims.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 35 lines · 18 tokens per session scan A 5b946a6f623a
apollyon-orchestrator is an agent published in the GitHub repository thedatakey/apollyon (1 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 298 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
owasp-data-specialist
OWASP A09 Security Logging and Monitoring Failures specialist for Enclave AI. Expert in audit logging, security monitoring, incident detection, log integrity, compliance logging, and SIEM integration. Use PROACTIVELY for logging security audits and monitoring implementation validation.
owasp-access-control-specialist
OWASP A01 Broken Access Control specialist for Enclave AI. Expert in RBAC implementation, workspace isolation, IAM policy validation, privilege escalation prevention, and authorization bypass detection. Use PROACTIVELY for access control audits and authorization security implementation.
owasp-crypto-specialist
OWASP A02 Cryptographic Failures specialist for Enclave AI. Expert in encryption implementation, key management, TLS configuration, hash functions, secure random generation, and cryptographic vulnerability detection. Use PROACTIVELY for cryptographic security audits and encryption implementation validation.
owasp-auth-specialist
OWASP A07 Identification and Authentication Failures specialist for Enclave AI. Expert in JWT security, OAuth2 flows, session management, credential storage, MFA implementation, and authentication bypass prevention. Use PROACTIVELY for authentication security audits and secure authentication implementation.
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…
owasp-injection-specialist
OWASP A03 Injection vulnerability specialist for Enclave AI. Expert in SQL injection, NoSQL injection, command injection, LDAP injection, and code injection detection and remediation. Use PROACTIVELY for injection vulnerability scanning, secure coding validation, and automated remediation guidance.