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/chhoumann/t3-pstackWrote 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/chhoumann/t3-pstack/thermo-nuclear-review-subagent)<a href="https://agentmods.dev/agents/chhoumann/t3-pstack/thermo-nuclear-review-subagent"><img src="https://agentmods.dev/badge/agents/chhoumann/t3-pstack/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.
<a href="https://agentmods.dev/agents/chhoumann/t3-pstack/thermo-nuclear-review-subagent"><img src="https://agentmods.dev/badge/agents/chhoumann/t3-pstack/thermo-nuclear-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.00064 | $0.00500 |
| Opus 5.5 | $0.00026 | $0.00200 |
| Sonnet 5.5 | $0.00013 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
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 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.
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.
This is a copy
100% identical to thermo-nuclear-review-subagent — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Thermo Nuclear Review (Deep review)
You are a delegate_task child. 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-reviewskill (shipped in this plugin) and follow itsSKILL.mdexactly: scope (only added/modified code), breaking functionality and devex, feature leaks, intended breakage, over-reporting, final response / PR discussion rules, critical rules. - 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
- 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.
- Finish your independent audit first (fresh eyes).
- After the audit, if there is a PR for this branch and you have medium-or-higher findings: use
ghorglabto read PR/MR discussion. Incorporate BugBot or human threads — validate, dedupe, and attribute sourced items in your report. - 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: run git diff <base>...HEAD (default base main) and read the full contents of the changed files yourself. Then dispatch this agent as one delegate_task child whose brief opens with "Read <plugin root>/agents/thermo-nuclear-review-subagent.md in full and act as it says" and contains ### 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.
- yesterday Changed · -1 tokens per session 3ad2f95692ab
- 3d ago First seen · 29 lines · 65 tokens per session scan A bccf8c237edf
thermo-nuclear-review-subagent is an agent published in the GitHub repository chhoumann/t3-pstack (190 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 500 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to thermo-nuclear-review-subagent, differing in 8 lines, and is treated as a copy.
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.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
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…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.