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/avelikiy/great_ctoWrote 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/avelikiy/great_cto/audit)<a href="https://agentmods.dev/commands/avelikiy/great_cto/audit"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/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.00020 | $0.04861 |
| Opus 5 | $0.00010 | $0.02431 |
| Sonnet 5 | $0.00004 | $0.00972 |
| Haiku 4.5 | $0.00002 | $0.00486 |
Grade A, and why
audit 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.
How it starts
The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Great CTO audit command for existing projects.
Fast by default (v1.0.43+): phases 1-4 run in parallel via sub-agents + CVE scan cached 24h. Typical runtime ~1-1.5 min on medium projects. No separate refresh mode — just re-run /audit.
Findings discipline (v1.0.106). Every finding in the audit report carries severity (low / med / high / critical) + one-line evidence with file:line or a concrete metric. Adjectives without numbers are not findings; handwavy claims without file references are guesses, not findings. See skills/great_cto/prose-style.md (RULE-H citation, RULE-08 claim calibration, RULE-03 concrete vs abstract).
Action: eval — run eval harness
If argument is eval (i.e. /audit eval):
EVAL_DIR="tests/eval"
ls "$EVAL_DIR"/EVAL-*.md 2>/dev/null | sort || echo "NO_EVALS"
If no eval files found:
No eval cases in tests/eval/.
Run /audit to create initial eval cases, or see tests/eval/ for the format.
If eval files exist — for each EVAL-*.md:
- Read the file — extract
## Assertionsbash block - Run each assertion
- Collect PASS / FAIL / WARN per assertion
- Report summary:
/audit eval — Eval Harness Results
EVAL-001 CRUD endpoint: PASS (3/3)
EVAL-002 Auth service: PASS (4/4)
EVAL-003 Discovery guard: WARN (manual verification needed)
EVAL-004 Hotfix nano: PASS (2/2)
EVAL-005 Security block: FAIL (1/3) — CSO report missing
Score: 4/5 passing | 1 failing | 1 manual
FAILURES:
EVAL-005: docs/security/CSO-*.md not found
→ Run the auth-service eval scenario first to generate the artifact
MANUAL CHECKS:
EVAL-003: discovery guard behavior requires live /start run
Exit after eval report. Do NOT proceed with normal audit.
Action: lint — scan artefacts against anti-pattern blocklist
If argument is lint (i.e. /audit lint):
Scans docs/architecture/, docs/threat-models/, docs/releases/SBOM-*.json,
docs/postmortems/, .great_cto/verdicts/ against rules in
skills/great_cto/references/anti-patterns.md. Advisory findings, not blocking.
Respects <!-- anti-pattern-waiver: <rule-id> reason:<why> --> lines.
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 · 402 lines · 20 tokens per session scan A 9e90dae3bde7
audit is a command published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 4,861 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-09-03.
Other commands, from other repositories
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Auto-creates PR unless --no-pr flag is passed.
fec-debug
Front-end problem diagnosis and repair: covering build failures, runtime errors, UI exceptions, and interface problems, using a unified diagnostic framework to classify problems by type.
fec-tdd
Use front-end TDD workflow to implement functions, fix bugs, or refactor logic: first write failing tests, then implement minimal code, and then refactor.
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
esp-debug
Help debug ESP32 crashes, hangs, and peripheral issues.
develop
Implement skill development issues with TDD-governed workflow.