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/initnpx skills add brian-lai/para-programming-plugin --skill initgit 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.00011 | $0.00586 |
| Opus 5 | $0.00005 | $0.00293 |
| Sonnet 5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
init 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize PARA-Programming structure in the current project.
Usage
/para:init
/para:init --template=basic # Minimal project CLAUDE.md (default)
/para:init --template=full # Comprehensive project CLAUDE.md
What It Does
- Set up global methodology file at
~/.claude/CLAUDE.md(copied fromresources/CLAUDE.mdif missing; never overwrites existing) - Create context directory structure:
mkdir -p context/{data,plans,summaries,archives,servers} - Create
context/context.mdseeded fromcontext-template.md:
See# Current Work Summary Ready to start first task. --- ```json { "active_context": [], "completed_summaries": [], "last_updated": "TIMESTAMP" } ```context-schema.mdfor the full field reference. - Create project
CLAUDE.md(if missing) fromclaude-basic-template.md(default,--template=basic) orclaude-full-template.md(--template=full) - Update
.gitignoreto include.para-worktrees/:- If
.gitignoreexists, check for.para-worktrees/entry; append if missing - If
.gitignoredoes not exist, create it with.para-worktrees/as its content - This prevents worktree directories from being tracked by git
- If
Success Output
After initialization, display:
PARA-Programming Structure Initialized
context/
├── archives/ # Historical context snapshots
├── data/ # Input files, payloads, datasets
├── plans/ # Pre-work planning documents
├── servers/ # MCP tool wrappers
├── summaries/ # Post-work reports
└── context.md # Active session context
.para-worktrees/ # Git worktree isolation (gitignored)
Files created/updated:
- ~/.claude/CLAUDE.md (global methodology, if it didn't exist)
- context/context.md (fresh context file)
- CLAUDE.md (project-specific context, if it didn't exist)
- .gitignore (added .para-worktrees/ entry)
Next steps:
1. Edit CLAUDE.md with your project-specific context
2. Create your first plan: /para:plan <task-description>
3. Check status: /para:status
4. Get help: /para:help
What ships with it
4 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.
- 2d ago First seen · 76 lines · 11 tokens per session scan A a43a3753fd7e
init is a skill published in the GitHub repository brian-lai/para-programming-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 586 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.
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…