pstack-claude is a set of opinionated coding-agent skills and workflows ported from Cursor to Claude Code, Codex, Pi, and other agent harnesses. It guides agents toward concise, simple, and verified code by routing goals to suitable workflows and supporting subagent tools. The catalogue entries are the project's skills, agents, hook, and plugin implementations for these agent environments.
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/michael-denyer/pstack-claudeWrote 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/michael-denyer/pstack-claude/thermo-nuclear-code-quality-review-subagent)<a href="https://agentmods.dev/agents/michael-denyer/pstack-claude/thermo-nuclear-code-quality-review-subagent"><img src="https://agentmods.dev/badge/agents/michael-denyer/pstack-claude/thermo-nuclear-code-quality-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/michael-denyer/pstack-claude/thermo-nuclear-code-quality-review-subagent"><img src="https://agentmods.dev/badge/agents/michael-denyer/pstack-claude/thermo-nuclear-code-quality-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.00068 | $0.00412 |
| Opus 5.5 | $0.00027 | $0.00165 |
| Sonnet 5.5 | $0.00014 | $0.00082 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
thermo-nuclear-code-quality-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- thermo-nuclear-code-quality-review — 88% identical, 12 lines differ
What it actually says
Thermo-Nuclear Code Quality Review
You are an Agent 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
- Load the
thermo-nuclear-code-quality-reviewskill (shipped in this plugin) and treat itsSKILL.mdas the complete rubric — tone, approval bar, output ordering, code-judo / 1k-line / spaghetti rules. - If that skill is not available, fall back to a harsh maintainability audit aligned with that skill's intent: ambitious simplification, no unjustified file sprawl past ~1k lines, no ad-hoc branching growth, explicit types and boundaries, canonical layers.
Work
- Apply the rubric only to what the diff and contents show. Trace cross-file impact when the change touches module boundaries.
- Output in the priority order the rubric specifies. Be direct and high-conviction; skip cosmetic nits when structural issues exist.
- 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, through the Explore agent when the set is large. Then invoke this agent with subagent_type: "pstack:thermo-nuclear-code-quality-review-subagent" and a user prompt containing ### 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 First seen · 24 lines · 68 tokens per session scan A 97506b3e4920
thermo-nuclear-code-quality-review-subagent is an agent published in the GitHub repository michael-denyer/pstack-claude (1,943 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 412 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-10-13.
Other agents, from other repositories
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
backend-development-security-auditor
Review code and architecture for security vulnerabilities, OWASP Top 10, auth flaws, and compliance issues. Use for security review during feature development.
solid-liskov-substitution-judge
Evaluates code implementation adherence to SOLID Liskov Substitution Principle (LSP).
ssot-judge
Evaluates implementation plans for SSOT (Single Source of Truth) violations.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…