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.
npx agentmods add skills/michael-denyer/pstack-claude/setup-pstacknpx skills add michael-denyer/pstack-claude --skill setup-pstackgit clone --depth 1 https://github.com/michael-denyer/pstack-claudeWhat 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 | $0.00059 | $0.01526 |
| Opus 5 | $0.00030 | $0.00763 |
| Sonnet 5 | $0.00012 | $0.00305 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade B, and why
setup-pstack scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Platform note.** On Codex or another non-Claude runtime, the override sheet is `~/.codex/pstack-models.md`, the slugs are your Codex models (for example `gpt-5.5`) not `claude-*`, and you load it by adding the sheet's How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup pstack
Write ~/.claude/pstack-models.md, a per-role model override sheet you include from your global CLAUDE.md. Each pstack skill names a default model inline; the override sheet is the layer that adapts those defaults to the models you actually have access to.
Platform note. On Codex or another non-Claude runtime, the override sheet is ~/.codex/pstack-models.md, the slugs are your Codex models (for example gpt-5.5) not claude-*, and you load it by adding the sheet's contents to ~/.codex/AGENTS.md (Codex has no @-include into a rules file). The role rows in step 5 are identical; only the slugs, the file path, and the load mechanism change. Detect Codex slugs from ~/.codex/config.toml (model = ...) plus whatever the user confirms. See codex-tools.md.
Claude Code has no auto-applied "rules" mechanism like Cursor's .mdc. Inclusion is explicit: the user adds a line to ~/.claude/CLAUDE.md (or their project CLAUDE.md) such as:
@~/.claude/pstack-models.md
so the file is loaded as context for every session.
Steps
1. Detect available models
Enumerate the model slugs you can pass to an Agent subagent in this session — that is the dependable source. The currently available Claude models and the default panel are listed in Models below; the quad is chosen for cross-family, cross-tier diversity, and the single-role default stays out of the panels because it already covers the single-model roles. Ask the user to confirm or paste any additional slugs they want available. Never write a real slug you have not confirmed is available. The aliases inherit-parent and auto are always valid even though they are not detected slugs; both mean the role runs on the parent session's model, which the Agent call expresses by omitting model.
2. Load current state
The default role-to-model mapping is the rule shape shown in step 5 below. If ~/.claude/pstack-models.md already exists, read it and treat its values as the current choices. Otherwise start from those defaults.
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.
- 2d ago First seen · 83 lines · 59 tokens per session scan B ee088dc3c49b
setup-pstack is a skill published in the GitHub repository michael-denyer/pstack-claude (142 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 1,526 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…