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/busycommitgit 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.00012 | $0.00800 |
| Opus 5 | $0.00006 | $0.00400 |
| Sonnet 5 | $0.00002 | $0.00160 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
busycommit 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 — 98 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 multiple atomic git commits, committing the smallest possible logical unit at a time
User arguments:
Busycommit: $ARGUMENTS
End of user arguments
Commit Message Rules
Follows Conventional Commits standard.
-
Format:
type(#issue): description- Use
#123for local repo issues - Use
owner/repo#123for cross-repo issues - Common types:
feat,fix,docs,refactor,test,chore
- Use
-
AI Credits: NEVER include AI credits in commit messages
- No "Generated with Claude Code"
- No "Co-Authored-By: Claude" or "Co-Authored-By: Happy"
- Focus on the actual changes made, not conversation history
-
Content: Write clear, concise commit messages describing what changed and why
Process
- Run
git statusandgit diffto review changes - Run
git log --oneline -5to see recent commit style - Stage relevant files with
git add - Create commit with descriptive message
- Verify with
git status
Example
git add <files>
git commit -m "feat(#123): add validation to user input form"
Atomic Commit Approach
Each commit should represent ONE logical change. Do NOT bundle multiple unrelated changes into one commit.
- Identify the smallest atomic units of change
- For EACH atomic unit: stage only those files/hunks, commit, verify
- Use
git add -pto stage partial file changes when a file contains multiple logical changes - Repeat until all changes are committed
- It is OK to create multiple commits without stopping - keep going until
git statusshows clean
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 · 98 lines · 12 tokens per session scan A 6e418dcfc6af
busycommit is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 800 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.