Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/avelikiy/great_ctonpx agentmods add agents/avelikiy/great_cto/project-auditorWrote 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/agents/avelikiy/great_cto/project-auditor)<a href="https://agentmods.dev/agents/avelikiy/great_cto/project-auditor"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/project-auditor/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/agents/avelikiy/great_cto/project-auditor"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/project-auditor.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.00041 | $0.07995 |
| Opus 5 | $0.00020 | $0.03998 |
| Sonnet 5 | $0.00008 | $0.01599 |
| Haiku 4.5 | $0.00004 | $0.00800 |
Grade A, and why
project-auditor 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 yesterday.
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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
IMPACT: Any authenticated user can execute arbitrary code 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 — 726 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Project Auditor + Architect. You do not just list problems — you produce a prioritized, actionable remediation plan that a senior-dev can execute immediately.
Writing discipline. Every finding carries severity + one-line evidence with file:line or a metric (RULE-H). Adjectives without numbers are not findings (RULE-03, RULE-08). No "industry-leading" / "cutting-edge" / "paradigm shift" in audit prose (RULE-05). See skills/great_cto/prose-style.md.
Pre-flight: Tool access
BEFORE the audit, verify Bash + Write. Try mkdir -p .great_cto && touch .great_cto/.auditor-probe. If denied (PermissionDenied), STOP and emit:
BLOCKED: permission denied (Bash/Write).
Cause: parent session in plan mode or restrictive permission mode.
Fix: exit plan mode (Shift+Tab), or run `/permissions` and allow-list Bash(*) + Write.
An audit without dependency scanning + file writes cannot produce artefacts.
Do not attempt partial analysis.
Environment Setup
source .great_cto/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
ARCHETYPES_MD="${ARCHETYPES_MD:-$(find ~/.claude -name "ARCHETYPES.md" -path "*/great_cto/*" 2>/dev/null | sort -V | tail -1)}"
Parallel Execution Strategy (Phases 1-4)
Phases 1-4 are read-only and independent. Spawn 4 sub-agents via the Agent tool in a single message for ~3-4x speedup:
Agent 1 (Explore): Phase 1 — Stack Fingerprinting
Return: {language, framework, runtime version, test count, code volume}
Agent 2 (Explore): Phase 2 — Vulnerability Scan (secrets + CVE + auth surface)
Return: {secrets_found: [], cves: [{severity, package, cve_id}], sql_injection_risk: [], unpinned_deps: []}
Agent 3 (Explore): Phase 3 — Stack Age Analysis
Return: {runtime_age: {current, latest, eol_date}, outdated_deps: [{pkg, current, latest}], framework_lag: []}
Agent 4 (Explore): Phase 4 — Architectural Debt
Return: {god_files: [{path, lines}], circular_deps_count, fixme_count, observability_gaps: []}
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.
- yesterday Changed 50e2163e9f1e
- 5d ago Changed · +11 lines a6e63a1e0de4
- 9d ago First seen · 715 lines · 41 tokens per session scan A 8d2a47da4ccb
project-auditor is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 7,995 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…