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/pr-askgit 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.00011 | $0.00941 |
| Opus 5 | $0.00005 | $0.00470 |
| Sonnet 5 | $0.00002 | $0.00188 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
pr-ask 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask - Request Review and Approval
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).
Ship/Show/Ask Pattern - ASK
Ask is for complex changes that need team discussion and approval. Examples:
- Breaking API changes
- New architecture decisions
- Significant feature additions
- Performance trade-offs
- Security-sensitive changes
When to Ask
Use Ask when:
- Changes affect multiple systems
- Breaking changes are needed
- You need input on approach
- Security implications exist
- Performance trade-offs need discussion
- Uncertain about the best solution
Workflow
Current branch status:
!git status
Recent commits:
!git log --oneline -5
User arguments:
Ask: $ARGUMENTS
End of user arguments
This is the traditional Pull Request workflow, but with explicit intent that review and approval are required.
Process:
-
Ensure Branch is Ready: !
git status- Commit all changes
- Push to remote:
git push origin [branch-name]
-
Create Ask PR: Create a PR that clearly needs review
Title: conventional commits format, prefixed with
[ASK]Description template:
## 🤔 Ask - Review and Approval Needed **This is an ASK PR**: These changes need team review and discussion. <!-- References: [link to relevant issues] --> ### What changed [Detailed description of changes] ### Why [Rationale and context] ### Questions for reviewers - [ ] Question 1 - [ ] Question 2 ### Concerns - Potential concern 1 - Potential concern 2 ### Test Plan - [ ] Unit tests - [ ] Integration tests - [ ] Manual testing steps ### Alternatives considered - Alternative 1: [why not chosen] - Alternative 2: [why not chosen]
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 · 164 lines · 11 tokens per session scan A f2ac3a5331b5
pr-ask is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 941 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-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.