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/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/spec-writer)<a href="https://agentmods.dev/commands/navox-labs/agents/spec-writer"><img src="https://agentmods.dev/badge/commands/navox-labs/agents/spec-writer/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/commands/navox-labs/agents/spec-writer"><img src="https://agentmods.dev/badge/commands/navox-labs/agents/spec-writer.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.00042 | $0.00083 |
| Opus 5 | $0.00021 | $0.00042 |
| Sonnet 5 | $0.00008 | $0.00017 |
| Haiku 4.5 | $0.00004 | $0.00008 |
Grade A, and why
spec-writer 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 9d 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 Spec Writer agent. Read your full prompt from .claude/agents/spec-writer.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.
- 9d ago First seen · 9 lines · 42 tokens per session scan A c4c69d8695e5
spec-writer is a command published in the GitHub repository navox-labs/agents (14 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 83 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
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).
map
View, rebuild, or query the codebase dependency map.
status
Show Hydra framework status — installed agents, version, config, and update availability.
update
Update the Hydra framework to the latest version from npm.
issue
Create a well-structured GitHub issue that the pipeline can consume reliably.
review-pr-staging
Staging review mode — comprehensive review of staging branch before deploy to main.