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/emaraschio/cursor-commandsWrote 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/commands/emaraschio/cursor-commands/thermo-nuclear-code-quality-review)<a href="https://agentmods.dev/commands/emaraschio/cursor-commands/thermo-nuclear-code-quality-review"><img src="https://agentmods.dev/badge/commands/emaraschio/cursor-commands/thermo-nuclear-code-quality-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.
<a href="https://agentmods.dev/commands/emaraschio/cursor-commands/thermo-nuclear-code-quality-review"><img src="https://agentmods.dev/badge/commands/emaraschio/cursor-commands/thermo-nuclear-code-quality-review.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.00029 | $0.00572 |
| Opus 5 | $0.00015 | $0.00286 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Extremely strict maintainability review that hunts for code-judo simplifications, giant files, and spaghetti-condition growth without changing behavior. Full workflow: .cursor/skill-contracts/thermo-nuclear-code-quality-review/SKILL.md (user install: ~/.cursor/skill-contracts/thermo-nuclear-code-quality-review/SKILL.md).
Defaults
| Setting | Default |
|---|---|
| Scope | current branch diff against its merge base |
| Posture | block on structural regressions; keep behavior identical |
| Findings | a few high-conviction comments over a long list of nits |
| Invocation | explicit only (do not auto-suggest) |
| Ship gate | A, S |
Steps
- Read
.cursor/skill-contracts/thermo-nuclear-code-quality-review/SKILL.mdfor the full agent contract; if that file is missing, read~/.cursor/skill-contracts/thermo-nuclear-code-quality-review/SKILL.md. - Execute the workflow in order; do not skip safety steps.
- Report outcomes per skill (summary, tables, or checklist as specified).
Anti-patterns
- Push for the code judo move, not surface polish. Trigger: a diff that works but carries avoidable structural complexity. Wrong: approving it or leaving only rename and style nits. Correct: name the code judo move that deletes whole branches or layers and push for it. Reason: a review that only polishes lets incidental complexity calcify into permanent debt.
- Block unjustified file-size and spaghetti growth. Trigger: a diff pushing a file past 1000 lines or bolting ad-hoc conditionals onto an unrelated flow. Wrong: accepting it because the tests pass. Correct: ask to decompose first and move the logic behind a dedicated abstraction. Reason: sprawl and scattered special cases make the surrounding code permanently harder to reason about.
Examples
/thermo-nuclear-code-quality-review/thermo-nuclear-code-quality-reviewscoped to a single file or module
Maintainers
Behavioral eval: .cursor/skill-contracts/thermo-nuclear-code-quality-review/eval/cases.md. Ship gate sections: A, S before changing SKILL.md or this command.
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.
- 9d ago First seen · 45 lines · 29 tokens per session scan A 819dff4eb33d
thermo-nuclear-code-quality-review is a command published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 572 once invoked, about $0.0001 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 commands, from other repositories
handle-pr-comments
Fetch all PR comments, classify by severity, and present for user approval before acting.
self-review
Review only changed files in this branch Your primary goal is to provide valuable, trustworthy feedback while avoiding false positives and low-impact commentary.
sdd-continue
Continue the next SDD phase in the dependency chain.
sdd-status
Show structured SDD status for an active change.
sdd-apply
Implement SDD tasks — writes code following specs and design.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.