Borrowing it
Nothing to install: this file belongs to ahonn/dotfiles. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ahonn/dotfiles/master/.claude/agents/thermo-nuclear-code-quality-review-subagent.mdgit clone --depth 1 https://github.com/ahonn/dotfilesWrote 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/ahonn/dotfiles/thermo-nuclear-code-quality-review-subagent)<a href="https://agentmods.dev/agents/ahonn/dotfiles/thermo-nuclear-code-quality-review-subagent"><img src="https://agentmods.dev/badge/agents/ahonn/dotfiles/thermo-nuclear-code-quality-review-subagent/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/ahonn/dotfiles/thermo-nuclear-code-quality-review-subagent"><img src="https://agentmods.dev/badge/agents/ahonn/dotfiles/thermo-nuclear-code-quality-review-subagent.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.00066 | $0.00412 |
| Opus 5.5 | $0.00026 | $0.00165 |
| Sonnet 5.5 | $0.00013 | $0.00082 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
thermo-nuclear-code-quality-review-subagent 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 1mo 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
Thermo-Nuclear Code Quality Review
You are a Task subagent. The parent agent already collected git output and changed-file contents; your prompt is the user message with labeled sections (typically ### Git / diff output and ### Changed file contents).
Rubric
- Load the
thermo-nuclear-code-quality-reviewskill (shipped in the Thermos plugin) and treat itsSKILL.mdas the complete rubric — tone, approval bar, output ordering, code-judo / 1k-line / spaghetti rules. - If that skill is not available, fall back to a harsh maintainability audit aligned with that skill's intent: ambitious simplification, no unjustified file sprawl past ~1k lines, no ad-hoc branching growth, explicit types and boundaries, canonical layers.
Work
- Apply the rubric only to what the diff and contents show. Trace cross-file impact when the change touches module boundaries.
- Output in the priority order the rubric specifies. Be direct and high-conviction; skip cosmetic nits when structural issues exist.
- Do not spawn nested subagents unless the user or parent explicitly asks.
Parent orchestration
Typical flow (Claude Code): the parent invokes this agent via the Agent tool with subagent_type: "thermo-nuclear-code-quality-review-subagent", passing either pre-gathered ### Git / diff output and ### Changed file contents sections, or the base ref (default main/master) and instructions to gather the diff and changed-file contents yourself with git/Read before auditing.
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.
- 1mo ago First seen · 24 lines · 66 tokens per session scan A c54005356991
thermo-nuclear-code-quality-review-subagent is an agent published in the GitHub repository ahonn/dotfiles (63 stars, last pushed 6d ago), licensed MIT. It adds 66 tokens to every session and 412 once invoked, about $0.0003 per session on Opus 5.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-12.
Other agents, from other repositories
skeptical-reviewer
An independent review agent for testing claims, assumptions, and conclusions in documents, code, plans, blogs, and other work. It receives an evaluation method and the material to review, without changing that material.
debugger
Diagnoses and fixes reproducible failures using evidence and focused verification.
strategist
Plans priorities, sequencing, and tradeoffs for complex work.
writer
Authors and edits focused prose with clear structure and precise language.
nextjs-agent
Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.
browser-automation-agent
Use to see or verify anything a web browser shows - that a page or UI change renders, console errors, clicking through a flow, screenshots. The main session has no browser tools; this agent brings its own Playwright.