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 instructions/brian-lai/para-programming-plugin/claude-mdgit 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.00517 | $0.00517 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
para-programming-plugin CLAUDE.md 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PARA-Programming Plugin
This document contains project-specific context only.
CRITICAL (MUST FOLLOW RULES)
Workflow Methodology: Follow the global workflow guide at ~/.claude/CLAUDE.md
Never commit directly to main. All code changes — including small fixes, version bumps, and one-liners — must go through the full PARA workflow: plan → worktree branch → PR → review → merge. There is no such thing as "too small for a PR."
If a request sounds like it could bypass this (e.g. "make a quick update", "just bump the version", "minor fix"), always ask the user for explicit confirmation before proceeding outside the workflow. Only skip if the user explicitly and directly instructs otherwise.
About This Project
The PARA-Programming Plugin is a CLI tool that implements the PARA (Plan → Review → Execute → Summarize → Archive) methodology for structured AI-assisted development workflows. It provides commands for managing planning documents, execution tracking, summaries, and context archival.
Tech Stack
- Language: TypeScript
- Runtime: Node.js
- CLI Framework: Custom command parsing
- File Operations: Node.js fs module
Structure
para-programming-plugin/
├── resources/ # Global CLAUDE.md methodology file
├── skills/ # Agent Skills (11 skills with co-located templates)
├── context/ # PARA workflow directories
│ ├── data/ # Input files, payloads, datasets
│ ├── plans/ # Pre-work planning documents
│ ├── summaries/ # Post-work reports
│ ├── archives/ # Historical context snapshots
│ └── servers/ # MCP tool wrappers
└── tests/ # Test suites
Key Files
resources/CLAUDE.md: Global workflow methodology templateskills/*/SKILL.md: Skill definitions with model/effort frontmatter
Conventions
- All context files use
YYYY-MM-DD-date prefixes for chronological sorting - Commands follow
/para:command-namenaming pattern - Markdown is used for all documentation and context files
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 · 62 lines · 517 tokens per session scan A c73da7e900f2
para-programming-plugin CLAUDE.md is an instructions file published in the GitHub repository brian-lai/para-programming-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 517 tokens to every session, about $0.0026 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.