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.
npx skills add michael-denyer/pstack-claude --skill principle-minimize-reader-loadgit 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/skills/michael-denyer/pstack-claude/principle-minimize-reader-load)<a href="https://agentmods.dev/skills/michael-denyer/pstack-claude/principle-minimize-reader-load"><img src="https://agentmods.dev/badge/skills/michael-denyer/pstack-claude/principle-minimize-reader-load/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/michael-denyer/pstack-claude/principle-minimize-reader-load"><img src="https://agentmods.dev/badge/skills/michael-denyer/pstack-claude/principle-minimize-reader-load.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00044 | $0.00415 |
| Opus 5.5 | $0.00018 | $0.00166 |
| Sonnet 5.5 | $0.00009 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
principle-minimize-reader-load 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- principle-minimize-reader-load — 100% identical, 0 lines differ
- principle-minimize-reader-load — 95% identical, 17 lines differ
- principle-minimize-reader-load — 95% identical, 14 lines differ
- principle-minimize-reader-load — 94% identical, 15 lines differ
- principle-minimize-reader-load — 94% identical, 2 lines differ
- principle-minimize-reader-load — 92% identical, 15 lines differ
- principle-minimize-reader-load — 88% identical, 2 lines differ
- principle-minimize-reader-load — 88% identical, 0 lines differ
What it actually says
Minimize Reader Load
Maintainability is the work a reader must do to understand code. Track two axes: layers to trace (indirections between the question and the answer) and state to hold (hidden or mutable context the reader must keep in their head). LOC, cyclomatic complexity, and "clean architecture" are proxies. Reader load is the thing that matters. The two axes are independent. A flat file with 50 globals can be as hard to reason about as a 6-layer adapter stack. Guard both. This is the human analog of Guard the Context Window. Working memory is finite for readers too.
- Collapse layers that cost more than they save: wrappers with one caller, adapters with no second implementation, speculative indirection that was never needed. Inline them.
- Make adjacent layers change the abstraction. A layer that repeats the same methods and arguments adds reader load without compression. Collapse pass-through layers.
- Demand interface compression. A broad interface that hides little complexity makes readers learn both the surface and the implementation. Prefer boundaries that hide meaningful decisions.
- Shrink state scope: prefer pure functions (returns over mutations), locals over fields, fields over module state, and module state over globals. Derive instead of sync.
- Name the invariant at the boundary, not in every consumer, so the reader learns it once.
- Before adding a layer or a piece of state, ask: does it reduce reader load elsewhere by at least as much?
The test: can a new reader answer "where does X come from?" and "what can change X?" in under 30 seconds? If not, cut layers or cut state.
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 Changed · -5 lines d10f8f6f185a
- 28d ago Changed 772bd55686c2
- 1mo ago Changed 002a973547e2
- 1mo ago First seen · 24 lines · 44 tokens per session scan A 0a3a24ec27c9
principle-minimize-reader-load is a skill published in the GitHub repository michael-denyer/pstack-claude (3,246 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 415 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
ln-33-plan-reviewer
Reviews a concrete implementation plan for missing decisions, feasibility and risk before execution; read-only.
ln-52-delivery-reviewer
Reviews a completed change for acceptance, regressions and release risk; read-only, not a whole-codebase audit.
ln-32-test-strategy-planner
Plans risk-based test portfolios and acceptance evidence; does not write or execute tests.
ln-41-surgical-change-implementer
Implements one scoped product feature or fix using existing contracts; not upgrades, performance tuning or establishing cross-cutting technical foundations.