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/brian-lai/para-programming-plugin/helpnpx skills add brian-lai/para-programming-plugin --skill helpgit clone --depth 1 https://github.com/brian-lai/para-programming-pluginWhat 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.00010 | $0.00556 |
| Opus 5 | $0.00005 | $0.00278 |
| Sonnet 5 | $0.00002 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
help 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 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.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Display the PARA-Programming quick-reference guide.
Usage
/para:help
Implementation
Display the following:
PARA-Programming Quick Reference
Workflow: Research → Plan → Review Plan → Execute → Review PR → Summarize → Archive
When to Use PARA
Use PARA if the task results in git changes (features, bug fixes, refactoring, config, migrations, tests, complex debugging).
Skip PARA if the task is read-only or informational (questions, navigation, explanations).
Commands
| Command | Purpose |
|---|---|
/para:init |
Initialize PARA structure in a project |
/para:research <task> |
Deep codebase research before planning |
/para:plan <task> |
Create a planning document (collaborative) |
/para:review --plan|--pr |
Staff+ FAANG engineer review loop |
/para:execute |
Create worktree, extract todos, start execution |
/para:workflow |
Orchestrate full execute → review → summarize → archive cycle |
/para:summarize |
Generate post-work summary |
/para:archive |
Archive context and start fresh |
/para:status |
Check current workflow state |
/para:check |
Decision helper: should I use PARA for this? |
/para:help |
Show this reference |
Typical Flow
/para:research Add user authentication
/para:plan Add user authentication
/para:review --plan
/para:workflow # or manually:
/para:execute # → Creates worktree, implements with TDD
/para:review --pr # → Staff+ review loop
/para:summarize # → Generate summary
/para:archive # → Clean up worktree
File Structure
context/
├── context.md # Active session context
├── plans/ # YYYY-MM-DD-task-name.md
├── summaries/ # YYYY-MM-DD-task-name-summary.md
├── archives/ # YYYY-MM-DD-context.md
├── data/ # Input/output files
└── servers/ # MCP tool wrappers
Tips
- Run
/para:statusto see where you are in the workflow - Run
/para:checkif unsure whether a task needs PARA - Full methodology details are in
~/.claude/CLAUDE.md
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 · 78 lines · 10 tokens per session scan A 91057b0267e5
help is a skill published in the GitHub repository brian-lai/para-programming-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 556 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.