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 commands/lhohan/claude-code-plugins/buildgit clone --depth 1 https://github.com/lhohan/claude-code-pluginsWhat 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.00020 | $0.02150 |
| Opus 5 | $0.00010 | $0.01075 |
| Sonnet 5 | $0.00004 | $0.00430 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
build 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 yesterday.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
The task you are helping me with is described in {{prompt}} .
System
When executing a task, NEVER begin writing code immediately. Always start with analysis and planning. Verify understanding of the task with the user BEFORE proposing implementation details.
Task Execution Process
Follow these steps in STRICT ORDER:
Setup
BEFORE beginning: create a new markdown file to capture your notes while you work on this issue. Save it in the notes directory with the same name as the markdown file passed: {{prompt}} . IF such a file already exists, read the file and continue from where you left off.
Required Notes File Structure
Your notes file MUST include these standardized sections for session continuity:
## Current Status
- **Phase**: [Current phase number and name]
- **Step**: [Current step within phase]
- **Last Updated**: [Timestamp]
## Phase Status Tracker
- ⏸️ Phase 1: Task Analysis - PENDING
- ⏸️ Phase 2: Solution Design - PENDING
- ⏸️ Phase 3: Implementation - PENDING
- ⏸️ Phase 4: Review - PENDING
- ⏸️ Phase 5: Submit - PENDING
- ⏸️ Phase 6: Iterate - PENDING
- ⏸️ Phase 7: Reflect - PENDING
- ⏸️ Phase 8: Clean Up - PENDING
Status Icons: ⏸️ PENDING | 🔄 IN PROGRESS | ✅ COMPLETED
Phase 1: Task Analysis
BEFORE STARTING: Update notes with "Phase 1: Task Analysis - IN PROGRESS 🔄"
- Load the task described in {{prompt}}.
- Summarize the task requirements and constraints in your own words
- Challenge requirements early. Always question whether the requested task or approach is correct and necessary
- Explicitly ask the user to confirm your understanding before proceeding
- Identify any ambiguities or points requiring clarification and ask about them
- Once your understanding of the issue has been confirmed, write a summary to your note file.
AFTER COMPLETION: Update notes with "Phase 1: Task Analysis - COMPLETED ✅"
Optional: Consider using research agents for codebase understanding if the task involves unfamiliar systems
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.
- yesterday First seen · 188 lines · 20 tokens per session scan A 99862996c180
build is a command published in the GitHub repository lhohan/claude-code-plugins (2 stars, last pushed 9mo ago), licensed MIT. It adds 20 tokens to every session and 2,150 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.