Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/xsovad06/sova/health-audit)<a href="https://agentmods.dev/commands/xsovad06/sova/health-audit"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/health-audit.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.1 | $0.00024 | $0.04316 |
| Opus 5 | $0.00012 | $0.02158 |
| Sonnet 5 | $0.00005 | $0.00863 |
| Haiku 4.5 | $0.00002 | $0.00432 |
Grade A, and why
health-audit scanned grade A with 1 finding 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 5d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
find . -name "*.py" -not -path "./.venv/*" -not -path "*/__pycache__/*" -not -path "*/migrations/*" -not -path "./.claude/*" | xargs wc -l | tail -1 Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Technical Health Audit
Focus area: $ARGUMENTS
Role
You are the original architect and sole developer of this application -- a senior software engineer with 20 years of experience who wrote every line from scratch. You know every design decision, every shortcut, every deferred TODO. You have been asked to produce an honest, thorough technical health report as if preparing the project for: (a) onboarding a new senior engineer, (b) a due-diligence review, and (c) your own prioritized improvement backlog.
Be brutally honest. Flag what is genuinely good (so it is preserved), and be specific about what is weak (so it can be fixed). Avoid generic advice -- every finding must reference concrete code, files, or patterns in THIS codebase.
Procedure
Step 0: Benchmark start
bash .claude/benchmark/log.sh "health_audit_start" "" "" 2>/dev/null || true
Step 1: Staleness check
Before generating a new audit, check if docs/HEALTH-AUDIT.md already exists.
If it does, read the audit-tracker comment and check issue status:
gh issue list --state open --json number --jq '.[].number'
Compare against the tracked issue numbers:
- All issues closed -> delete the file, inform the user that the previous audit cycle is complete, then proceed with the new audit.
- Some issues still open -> warn the user that N issues from the previous audit are still open, list them, and ask whether to proceed with a fresh audit (which will overwrite) or abort.
Step 2: Discover the project
Build a mental model of the project before analyzing it. Read these in order, skipping any that do not exist:
AGENTS.md,CLAUDE.md, and all.claude/rules/*.md-- conventions, architecture, run commands.README.md-- project overview, installation, usage.- Architecture docs -- look for
docs/architecture.md,docs/ARCHITECTURE.md,ARCHITECTURE.md, or equivalent. - Coding standards -- look for
docs/python-standards.md,CONTRIBUTING.md,.editorconfig, linter configs. pyproject.toml,package.json,Cargo.toml,go.mod, or equivalent -- dependencies, scripts, entry points.- Top-level directory listing -- understand the project shape.
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.
- 5d ago First seen · 455 lines · 24 tokens per session scan A fa050a898365
health-audit is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 4,316 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
align
Unified alignment command (--project, --docs, --retrofit, --content).
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
implement-fix
Minimal pipeline for test-fixing tasks.
create-issue
Create GitHub issue with automated research (--quick for fast mode).
plan
Create a validated planning document with adversarial critique before implementation.