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 psd401/psd-claude-plugins --skill plangit clone --depth 1 https://github.com/psd401/psd-claude-pluginsWrote 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/psd401/psd-claude-plugins/plan)<a href="https://agentmods.dev/skills/psd401/psd-claude-plugins/plan"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/plan/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/psd401/psd-claude-plugins/plan"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/plan.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.00048 | $0.01028 |
| Opus 5.5 | $0.00019 | $0.00411 |
| Sonnet 5.5 | $0.00010 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
plan 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PLAN — clarify, research, design, define done
The single planning surface. It scales from a quick fix to a full feature. It absorbs the old /architect, /brainstorm, /scope, /product-manager, /deepen-plan, and /issue. Its output is always the same shape: a task breakdown plus a machine-checkable Definition of Done — the exact contract /lfg drives to.
Capture the intent behind the request, not just the request — who the work is for and what it unblocks shapes the design more than any checklist. The phases below are the shape of the output; scale your depth within them to the problem.
Target: $ARGUMENTS
Contracts: docs/patterns/definition-of-done.md, docs/patterns/issue-contract.md.
Phase 1: Clarify first (don't code the wrong thing)
Surface the unknowns before designing. Ask the sharp questions a senior engineer would — edge cases, failure modes, scope boundaries, who the user is, what "done" means. Use AskUserQuestion for the few decisions that genuinely change the design. Keep going until you could write a testable Definition of Done without guessing.
If $ARGUMENTS is an existing issue number, read it (gh issue view N --comments) and refine rather than restart.
Phase 2: Size it
- Small (a fix, a contained change) → skip straight to a tight DoD + a short task list.
- Medium (a feature) → research + design + DoD + task breakdown.
- Large (a system / multi-surface effort) → add architecture and a short PRD section (problem, users, success metrics, risks), then decompose into several contract-compliant issues.
State which size you picked and why.
Phase 3: Research (parallel)
Dispatch in parallel via Task (skip any that don't apply):
- learnings-researcher — prior learnings in this repo.
- repo-research-analyst — how this codebase does this today; conventions to follow.
- best-practices-researcher / framework-docs-researcher — external patterns, and confirm nothing recommended is deprecated.
- spec-flow-analyzer — user-flow permutations and edge cases.
- architect-specialist (large only) — architecture options and trade-offs.
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.
- 14d ago Changed · -1 lines 41734836ddd8
- 1mo ago Changed e13ca4c36341
- 2mo ago First seen · 82 lines · 48 tokens per session scan A 3865f7d8857e
plan is a skill published in the GitHub repository psd401/psd-claude-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 48 tokens to every session and 1,028 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-31.
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…