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/AnastasiyaW/codex-claude-code-configWrote 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/anastasiyaw/codex-claude-code-config/thermo-nuclear-code-quality-review)<a href="https://agentmods.dev/agents/anastasiyaw/codex-claude-code-config/thermo-nuclear-code-quality-review"><img src="https://agentmods.dev/badge/agents/anastasiyaw/codex-claude-code-config/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.00046 | $0.00149 |
| Opus 5 | $0.00023 | $0.00075 |
| Sonnet 5 | $0.00009 | $0.00030 |
| Haiku 4.5 | $0.00005 | $0.00015 |
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 8d 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
Strict Quality Reviewer
The parent supplies the diff and changed-file contents. Read the matching skill, apply its evidence/materiality screen, and return only prioritized findings or a clean verdict. Do not fix code, approve based on the builder's narrative, or spawn nested reviewers.
Source
Adapted from Cursor Team Kit's MIT-licensed reviewer agent: https://github.com/cursor/plugins/tree/main/cursor-team-kit/agents/thermo-nuclear-code-quality-review.md
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.
- 8d ago First seen · 17 lines · 46 tokens per session scan A a5b66095b86d
thermo-nuclear-code-quality-review is an agent published in the GitHub repository AnastasiyaW/codex-claude-code-config (149 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 149 once invoked, about $0.0002 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-30.
Other agents, from other repositories
skill-reviewer
Evaluates skill file quality against optimization patterns and editing principles. Returns structured quality report with grade, issues, and fix suggestions. Use when reviewing created or modified skill content.
verifier
Fresh-eyes, coverage-first quality judge for sweep passes on any deliverable (code, UI, copy, video frames, research, prompts). Use PROACTIVELY after producing work, one invocation per dimension or lens. Give it the rubric (or the craft file path), the evidence (file paths, screenshot paths, run output), and the lens…
tldrcrew-reviewer
Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.
lean-crew-reviewer
Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
Gilfoyle Code Review Mode
Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley. Prepare for brutal honesty about your code.