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 skills add chhoumann/t3-pstack --skill setup-pstackgit clone --depth 1 https://github.com/chhoumann/t3-pstackWrote 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/skills/chhoumann/t3-pstack/setup-pstack)<a href="https://agentmods.dev/skills/chhoumann/t3-pstack/setup-pstack"><img src="https://agentmods.dev/badge/skills/chhoumann/t3-pstack/setup-pstack/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/skills/chhoumann/t3-pstack/setup-pstack"><img src="https://agentmods.dev/badge/skills/chhoumann/t3-pstack/setup-pstack.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.00067 | $0.02010 |
| Opus 5.5 | $0.00027 | $0.00804 |
| Sonnet 5.5 | $0.00013 | $0.00402 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade A, and why
setup-pstack 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup pstack
Write the model sheet, ~/.config/t3-pstack/models.md ($XDG_CONFIG_HOME/t3-pstack/models.md when that is set), one per machine. It sets pstack's T3 provider and model per role, and every pstack skill reads it before it dispatches.
Steps
1. Detect available models
Call orchestrator_capabilities, or acp-mcp-call orchestrator_capabilities '{}' where the T3 tools are not exposed. Its provider instances and their models are the dependable source. A target is valid only when its provider instance can run a child task and lists the model. Note each provider's own option IDs and values, such as effort on Claude and reasoningEffort on Codex and Grok. Never write a target you have not seen there. The aliases inherit-parent and auto are always valid.
2. Load current state
The default role-to-target mapping is the sheet shape in step 5 below. If the sheet already exists, read it and treat its # budget line and its role values as the current choices. If it does not, read t3-pstack-models.md in the host's config directory ($CLAUDE_CONFIG_DIR or ~/.claude on Claude Code, $CODEX_HOME or ~/.codex on Codex), where releases before 2.0.0-rc.3 kept the sheet, the same way. Otherwise start from those defaults. A line whose role is not in step 5, such as how critics, is from a retired role. Drop it. Carry a strongest judgment value over to hardest tasks, its new name. Also drop any value that is not a T3 entry, such as a bare family name, a claude- slug, or an @<level> suffix, and a default effort line.
3. Budget, map, and confirm
(a) Ask for a budget. Ask a structured multiple-choice question (AskUserQuestion on Claude Code, numbered options in plain text elsewhere). Offer these four options with these exact labels, and name the current budget when the sheet records one. With no sheet, say that large matches the skill defaults.
unlimited - max reasoninglarge - xhigh reasoningmedium - high reasoningsmall - medium reasoning
What ships with it
2 files 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.
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 · -46 lines · +11 tokens per session 8f03d5785404
- 3d ago First seen · 120 lines · 56 tokens per session scan A c36851047c32
setup-pstack is a skill published in the GitHub repository chhoumann/t3-pstack (190 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 2,010 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…