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/wbern/agent-instructions/summarizegit clone --depth 1 https://github.com/wbern/agent-instructionsWhat 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.00008 | $0.00481 |
| Opus 5 | $0.00004 | $0.00241 |
| Sonnet 5 | $0.00002 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
summarize 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Guidelines
Output Style
- Never explicitly mention TDD in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use mcp__beads__* tools to manage issues (the user interacts via bd commands).
Plan File Restriction
NEVER create, read, or update plan.md files. Claude Code's internal planning files are disabled for this project. Use other methods to track implementation progress (e.g., comments, todo lists, or external tools).
Create a concise summary of the current conversation suitable for transferring context to a new conversation.
User arguments:
Summarize: $ARGUMENTS
End of user arguments
Summary Structure
Provide a summary with these sections:
What We Did
- Key accomplishments and changes made
- Important decisions or discoveries
- Files created, modified, or analyzed
What We're Doing Next
- Immediate next steps
- Pending tasks or work in progress
- Goals or objectives to continue
Blockers & User Input Needed
- Any issues requiring user intervention
- Decisions that need to be made
- Missing information or clarifications needed
Output Format
Keep the summary concise and actionable - suitable for pasting into a new conversation to quickly restore context without needing the full conversation history.
Beads Integration
If Beads MCP is available, check for task tracking status and ask if the user wants to:
- Review current task status
- Update task states based on conversation progress
- Include Beads context in the summary
Use AskUserQuestion to confirm Beads integration preferences.
Testing Requirements
| Change | Required |
|---|---|
| Content (fragment/source) | Snapshot update |
| Feature flag | Conditional test (enabled + disabled), FLAG_OPTIONS, CLI mock |
| CLI option | cli.test.ts mock |
| Generation logic | Unit test |
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 · 74 lines · 8 tokens per session scan A 89a07030a47e
summarize is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 481 once invoked, about $0.0000 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-30.
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.