A review workflow that runs separate checks for bugs and security issues, and for code quality and maintainability, then combines their findings.

Use it to audit changed files for breakages, security risks, feature-flag leaks, poor structure, excessive growth, or maintenance problems.

It gives a branch or change set two different kinds of review instead of relying on one pass to find every problem.

thermos — Skill for Claude Code by chhoumann/t3-pstack

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 chhoumann/t3-pstack --skill thermos

Clone the repo

git clone --depth 1 https://github.com/chhoumann/t3-pstack

Made for: Claude Code.

Or install t3-pstack, the plugin that ships this one along with the rest of its 62 skills, 4 agents, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chhoumann/t3-pstack/thermos/github.svg)](https://agentmods.dev/skills/chhoumann/t3-pstack/thermos)

Your own site

<a href="https://agentmods.dev/skills/chhoumann/t3-pstack/thermos"><img src="https://agentmods.dev/badge/skills/chhoumann/t3-pstack/thermos/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/chhoumann/t3-pstack/thermos"><img src="https://agentmods.dev/badge/skills/chhoumann/t3-pstack/thermos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 432 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 92% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.00432
Opus 5.5	$0.00016	$0.00173
Sonnet 5.5	$0.00008	$0.00086
Haiku 4.5	$0.00004	$0.00043

Measured yesterday against content hash fbaba832f64a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

thermos 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.

Origin

This is a copy

92% identical to thermos — 11 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.

plugins/pstack/skills/thermos/SKILL.md · 22 lines

What it actually says

Thermos

Run the two thermo review passes as async background subagents in parallel, then synthesize their results.

Workflow

Determine the review scope from the user request, PR, current branch, or relevant changed files.
Gather the diff and any file/context excerpts needed for reviewers to evaluate the change without guessing.
Launch both subagents in the same response as two delegate_task calls with mode: "async" and role: "review", on the first two model families of the interrogate reviewers sheet line (<plugin root> is the directory that holds this plugin's skills/):
- a brief that opens with "Read <plugin root>/agents/thermo-nuclear-review-subagent.md and <plugin root>/skills/thermo-nuclear-review/SKILL.md in full and act as they say" for bugs, breakages, security, devex regressions, feature-flag leaks, and other branch-audit risks.
- a brief that opens with "Read <plugin root>/agents/thermo-nuclear-code-quality-review-subagent.md and <plugin root>/skills/thermo-nuclear-code-quality-review/SKILL.md in full and act as they say" for maintainability, structure, file-size growth, spaghetti, abstractions, and codebase-health risks.
Pass each subagent the same scoped diff/file context and ask it to return prioritized findings with file references and evidence.
After both finish, synthesize the results with findings first, deduplicated across reviewers. Weight overlapping findings more heavily, resolve disagreements with your own judgment, and keep summaries brief.

If individual background summaries are already visible to the user, do not restate them wholesale. Surface the unified verdict, the highest-signal findings, and any remaining uncertainty.

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.

yesterday Changed · -3 lines fbaba832f64a
3d ago First seen · 25 lines · 39 tokens per session scan A b1456cb4ba28

Subscribe to this mod's changes

thermos is a skill published in the GitHub repository chhoumann/t3-pstack (190 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 432 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to thermos, differing in 11 lines, and is treated as a copy.

Code review Debugging

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart. Do not use for ordinary review, style feedback, or general improvement suggestions.

emdash-cms/emdash · 62 tokens

gsd-ns-review

quality gates | code review debug audit security eval ui.

open-gsd/gsd-core · 16 tokens

gitnexus

A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.

hashgraph-online/awesome-codex-plugins · 58 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

cleanup-code-inspections

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

flutter/flutter-intellij · 19 tokens

superlint

This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.

mgechev/skillgrade · 0 tokens