thermo-nuclear-review

thermo-nuclear-review is a skill for Claude Code from asteasolutions/ai-toolkit. It costs 59 tokens per session (891 once invoked), scanned A, original, MIT.

A review procedure for checking the changes on a code branch or pull request for bugs, security problems, broken behavior, and development-workflow issues. A branch is a separate line of code changes, and a pull request is a proposal to merge those changes.

In plain words
What is it for?
Use it for thorough security and correctness audits of branch or pull-request changes, including possible breakage, secret-handling problems, and changes that make local development harder.
Why use it?
It helps find problems introduced by the current changes before they reach the main codebase. The review is limited to added or modified code rather than unrelated older code.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it for thorough security and correctness audits of branch or pull-request changes, including possible breakage, secret-handling problems, and changes that make local development harder.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asteasolutions/ai-toolkit/thermo-nuclear-review
Install

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.

Any agent
npx skills add asteasolutions/ai-toolkit --skill thermo-nuclear-review
Clone the repo
git clone --depth 1 https://github.com/asteasolutions/ai-toolkit

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/asteasolutions/ai-toolkit/thermo-nuclear-review"><img src="https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/thermo-nuclear-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 891 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.00059 $0.00891
Opus 5 $0.00030 $0.00445
Sonnet 5 $0.00012 $0.00178
Haiku 4.5 $0.00006 $0.00089

Measured 10d ago against content hash f3c26cfe1f76, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

thermo-nuclear-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 10d 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/skills/thermo-nuclear-review/SKILL.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Thermo Nuclear Review

Use this skill for a comprehensive security and correctness audit of a checked-out branch.

Prompt

You are a security expert performing a comprehensive review of a checked out branch. Audit this branch and its changes extremely thoroughly for bugs, changes that break existing features/functionality, and security vulnerabilities. Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.

Scope

ONLY report issues related to code that is being ADDED or MODIFIED in this PR. Focus on changes in the diff. DO NOT report vulnerabilities in existing code that is not being changed.

Guidelines

Breaking Functionality Guidelines

This is a complex codebase, with many cross-package/module dependencies. Often simple code changes in one place have subtle interactions that break functionality elsewhere. You MUST be extremely thorough in tracing through possible side effects of the changes.

Breaking Devex Guidelines

It can be easy to break developers' ability to run / build the code locally. You MUST catch changes that will impact users' developer experience. Some examples (not exhaustive):

  • Modifying how secrets are read / where they are read from
  • Updating environment variable names / adding environment variables
  • Remapping ports / networking
  • Adding scripts that must be run for certain functionality to continue working. Broadly speaking these are changes that will modify the way developers currently run / build the code. This does not include changes that introduce new alternative ways to run/build things. Adding dependencies with package managers does not count as a devex breaking change, unless it requires the user to do some very new thing that is not part of their normal development workflow, like manually installing software off of a website / App Store.

Feature Leak Guidelines

The codebase might carefully gate features behind feature flags or internal-only checks. You MUST NOT allow any features that are meant to be behind a feature gate leak. These leaks are often subtle. Be VERY careful and thorough.

Read the full file on GitHub · 51 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 51 lines · 59 tokens per session scan A f3c26cfe1f76

Subscribe to this mod's changes

thermo-nuclear-review is a skill published in the GitHub repository asteasolutions/ai-toolkit (5 stars, last pushed 9d ago), licensed MIT. It adds 59 tokens to every session and 891 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.