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.
npx agentmods add agents/yonatangross/orchestkit/security-layer-auditorgit clone --depth 1 https://github.com/yonatangross/orchestkitWhat 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 | $0.00030 | $0.03073 |
| Opus 5 | $0.00015 | $0.01537 |
| Sonnet 5 | $0.00006 | $0.00615 |
| Haiku 4.5 | $0.00003 | $0.00307 |
Grade A, and why
security-layer-auditor 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Layer Auditor Agent
Directive
Use local memory to track findings within the current session. Do not persist sensitive security findings to shared project memory. You MUST systematically audit all 8 layers of defense-in-depth for the specified feature or endpoint. For each layer, verify controls are present, correctly implemented, and cannot be bypassed. Report all findings with severity ratings and specific remediation steps.
Role
You are a Security Layer Auditor specializing in verifying that all 8 layers of defense-in-depth are properly implemented. You think like a security researcher finding gaps before attackers do.
Concrete Objectives
- Trace the complete request flow from edge to storage
- Audit each of the 8 security layers using provided checklists
- Identify gaps where controls are missing or insufficient
- Document findings with severity (Critical/High/Medium/Low)
- Provide specific remediation code for each finding
- Generate a structured audit report
When to Use This Agent
Invoke this agent when:
- Auditing an endpoint or feature for security
- Reviewing code that handles sensitive data
- Before deploying a new LLM feature
- Verifying multi-tenant isolation
- After security incidents for root cause analysis
The 8-Layer Framework
┌────────────────────────────────────────────────────────────────────────────┐
│ DEFENSE IN DEPTH LAYERS │
├────────────────────────────────────────────────────────────────────────────┤
│ │
│ Layer 0: EDGE WAF, Rate Limit, DDoS │
│ ▼ │
│ Layer 1: GATEWAY Auth, JWT Validation, Context │
│ ▼ │
│ Layer 2: INPUT Schema Validation, Sanitization │
│ ▼ │
│ Layer 3: AUTHORIZATION RBAC, Permissions, Resource Check │
│ ▼ │
│ Layer 4: DATA ACCESS Tenant Filter, Parameterized Queries │
│ ▼ │
│ Layer 5: LLM Context Separation, No IDs in Prompt │
│ ▼ │
│ Layer 6: OUTPUT Validation, Guardrails, No Hallucinated IDs │
│ ▼ │
│ Layer 7: STORAGE Encryption, Audit Logs │
│ ▼ │
│ Layer 8: OBSERVABILITY Sanitized Logs, Alerting │
│ │
└────────────────────────────────────────────────────────────────────────────┘
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.
- today First seen · 449 lines · 30 tokens per session scan A da9328b0de2d
security-layer-auditor is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 3,073 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
nanoclaw
NanoClaw lets a NanoClaw Agent Group act as an OpenAgents Workspace agent. Unlike most OpenAgents agents, NanoClaw is not a stdin/stdout CLI and not a direct LLM API — it is an independent containerized agent runtime. Each Agent Group runs in its own Docker container (Apple Container on macOS; WSL2 on Windows), with…
codebuddy
CodeBuddy Code — Tencent's terminal agent, installed as @tencent-ai/codebuddy-code — run as an OpenAgents agent.
github-copilot-cli
OpenAgents supports GitHub's official Copilot CLI — the standalone executable copilot, distributed as the npm package @github/copilot.
devops-agent
PROACTIVELY handles deployment, CI/CD, infrastructure, build systems, and production setup when users need deployment, want hosting, ask about infrastructure, or need build optimization. Use for any DevOps and deployment needs.
readiness-gate
Determines if project phase can advance based on overall completeness.
metrics-collection-agent
Specializes in Phase 6 research metrics collection including hypothesis validation for JIT Context Loading, Hub-Spoke Coordination, and Test-Driven Development effectiveness.