dotfiles: Agent for Claude Code

.claude/agents/thermo-nuclear-review-subagent.md

thermo-nuclear-review-subagent is an agent for Claude Code from ahonn/dotfiles. It costs 63 tokens per session (497 once invoked), scanned A, original, MIT.

A review agent that audits only the changed code in a branch for bugs, breaking changes, security problems, developer experience issues, and leaked feature flags. It can also account for relevant pull-request or merge-request discussion when available.

In plain words
What is it for?
Use it to inspect a code diff before merging, trace effects across packages, and report evidence-based issues for a pull request.
Why use it?
It gives a focused second review without treating untouched, pre-existing code as part of the change.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents; mentions Claude Code.

This is ahonn/dotfiles's own configuration. It tells Claude Code how to work on dotfiles itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dotfiles configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/ahonn/dotfiles/master/.claude/agents/thermo-nuclear-review-subagent.md
Clone the repo
git clone --depth 1 https://github.com/ahonn/dotfiles

Made for: Claude Code.

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.

agentmods badge for thermo-nuclear-review-subagent

README.md
[![agentmods](https://agentmods.dev/badge/agents/ahonn/dotfiles/thermo-nuclear-review-subagent/github.svg)](https://agentmods.dev/agents/ahonn/dotfiles/thermo-nuclear-review-subagent)
Your own site
<a href="https://agentmods.dev/agents/ahonn/dotfiles/thermo-nuclear-review-subagent"><img src="https://agentmods.dev/badge/agents/ahonn/dotfiles/thermo-nuclear-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.

agentmods 80×15 button for thermo-nuclear-review-subagent

Your own site · 80×15
<a href="https://agentmods.dev/agents/ahonn/dotfiles/thermo-nuclear-review-subagent"><img src="https://agentmods.dev/badge/agents/ahonn/dotfiles/thermo-nuclear-review-subagent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 497 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.00497
Opus 5.5 $0.00025 $0.00199
Sonnet 5.5 $0.00013 $0.00099
Haiku 4.5 $0.00006 $0.00050

Measured 1mo ago against content hash 08aeec4cff9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

thermo-nuclear-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.

.claude/agents/thermo-nuclear-review-subagent.md · 29 lines

What it actually says

Thermo Nuclear Review (Deep 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

  1. Load the thermo-nuclear-review skill (shipped in the Thermos plugin) and follow its SKILL.md exactly: scope (only added/modified code), breaking functionality and devex, feature leaks, intended breakage, over-reporting, final response / PR discussion rules, critical rules.
  2. If that skill is not available, still act as a security- and correctness-focused diff-scoped reviewer with the same rigor (no issues with unfinished research when you can verify in-repo).

Work

  1. Perform the full audit against only the changed code in the diff. Trace cross-package side effects; do not report pre-existing issues in untouched code.
  2. Finish your independent audit first (fresh eyes).
  3. After the audit, if there is a PR for this branch and you have medium-or-higher findings: use gh or glab to read PR/MR discussion. Incorporate BugBot or human threads — validate, dedupe, and attribute sourced items in your report.
  4. Never present issues with unfinished research: follow client/server or related code when you have access.

Calibrate severity honestly. Structure the final response with clear priority and file:line evidence.

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-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.

Changes

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.

  1. 1mo ago First seen · 29 lines · 63 tokens per session scan A 08aeec4cff9f

Subscribe to this mod's changes

thermo-nuclear-review-subagent is an agent published in the GitHub repository ahonn/dotfiles (63 stars, last pushed 6d ago), licensed MIT. It adds 63 tokens to every session and 497 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.