Borrowing it
Nothing to install: this file belongs to Edison-Watch/Custom-MCPs. 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/Edison-Watch/Custom-MCPs/main/.claude/agents/thermo-nuclear-code-quality-review.mdgit clone --depth 1 https://github.com/Edison-Watch/Custom-MCPsWrote 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/edison-watch/custom-mcps/thermo-nuclear-code-quality-review)<a href="https://agentmods.dev/agents/edison-watch/custom-mcps/thermo-nuclear-code-quality-review"><img src="https://agentmods.dev/badge/agents/edison-watch/custom-mcps/thermo-nuclear-code-quality-review.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.00063 | $0.00439 |
| Opus 5 | $0.00032 | $0.00219 |
| Sonnet 5 | $0.00013 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
thermo-nuclear-code-quality-review 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 6d 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
- Read the rubric file
.claude/skills/thermo-nuclear-code-quality-review/SKILL.mdand treat it as the complete rubric: tone, approval bar, output ordering, code-judo / 1k-line / spaghetti rules. (The skill setsdisable-model-invocation, so read the file directly rather than invoking it as a skill.) - If that file is not present, fall back to a harsh maintainability audit aligned with its 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: the parent collects git diff <base>...HEAD (default base main) directly via Bash, and gathers the full contents of the changed files (a Task with subagent_type: "Explore" works well when there are many files). Then invoke this agent with subagent_type: "thermo-nuclear-code-quality-review" and a user prompt containing ### Git / diff output and ### Changed file contents.
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.
- 6d ago First seen · 24 lines · 63 tokens per session scan A 58acd61383d6
thermo-nuclear-code-quality-review is an agent published in the GitHub repository Edison-Watch/Custom-MCPs (0 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 439 once invoked, about $0.0003 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-31.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.