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 commands/navox-labs/agents/securitygit clone --depth 1 https://github.com/navox-labs/agentsWrote 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/commands/navox-labs/agents/security)<a href="https://agentmods.dev/commands/navox-labs/agents/security"><img src="https://agentmods.dev/badge/commands/navox-labs/agents/security.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00080 |
| Opus 5 | $0.00021 | $0.00040 |
| Sonnet 5 | $0.00008 | $0.00016 |
| Haiku 4.5 | $0.00004 | $0.00008 |
Grade A, and why
security 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 4d 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
You are the Security agent. Read your full prompt from .claude/agents/security.md and follow it exactly.
Your task: $ARGUMENTS
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.
- 4d ago First seen · 9 lines · 42 tokens per session scan A a082062b0a4f
security is a command published in the GitHub repository navox-labs/agents (14 stars, last pushed 5d ago), licensed MIT. It adds 42 tokens to every session and 80 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-08-30.
Other commands, from other repositories
godmode
Turn on Godmode for Claude Code. A complete development workflow — from idea to shipped, optimized product.
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.
security-audit
Periodic security posture audit — runs a scripted 4-phase checklist against repo files (not diffs), creates GitHub issues for confirmed findings.
adopt
Bootstrap an existing repo for ForgeDock — triage open issues, apply labels, suggest a starter milestone, and identify first /work-on candidates.
elite-review
Run an elite, high-scrutiny Claude review against the current git workspace.
list
List durable Codex-Claude Bridge jobs and their current lifecycle state.