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/issuegit 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.00010 | $0.01511 |
| Opus 5 | $0.00005 | $0.00756 |
| Sonnet 5 | $0.00002 | $0.00302 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
issue 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.
This is a copy
86% identical to cycle — 82 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze GitHub issue and create TDD implementation plan.
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).
Process:
- Get Issue Number
User arguments:
Issue: $ARGUMENTS
End of user arguments
- Check if argument is an issue number
- Otherwise try branch name patterns: issue-123, 123-feature, feature/123, fix/123
- If not found: ask user
- Fetch Issue
Try to fetch the issue using GitHub MCP (mcp__github__issue_read tool).
If GitHub MCP is not configured, show:
GitHub MCP not configured!
See: https://github.com/modelcontextprotocol/servers/tree/main/src/github
Trying GitHub CLI fallback...
Then try using gh issue view [ISSUE_NUMBER] --json as fallback.
- Analyze and Plan
Summarize the issue and requirements, then:
Discovery Phase
Understand the requirement by asking (use AskUserQuestion if needed):
Problem Statement
- What problem does this solve?
- Who experiences this problem?
- What's the current pain point?
Desired Outcome
- What should happen after this is built?
- How will users interact with it?
- What does success look like?
Scope & Constraints
- What's in scope vs. out of scope?
- Any technical constraints?
- Dependencies on other systems/features?
Context Check
- Search codebase for related features/modules
- Check for existing test files that might be relevant
Beads Integration
Use Beads MCP to:
- Track work with
bd readyto find next task - Create issues with
bd create "description" - Track dependencies with
bd dep add
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 · 173 lines · 10 tokens per session scan A 9949ac5008f6
issue is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 1,511 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to cycle, differing in 82 lines, and is treated as a copy.
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.