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/redgit 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.01280 |
| Opus 5 | $0.00005 | $0.00640 |
| Sonnet 5 | $0.00002 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
red 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
91% identical to cycle — 16 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User arguments:
Red: $ARGUMENTS
End of user arguments
RED PHASE! Apply the below to the user input above.
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).
(If there was no info above, fallback to:
- Context of the conversation, if there's an immediate thing
bd readyto see what to work on next and start from there)
TDD Fundamentals
The TDD Cycle
The foundation of TDD is the Red-Green-Refactor cycle:
-
Red Phase: Write ONE failing test that describes desired behavior
- The test must fail for the RIGHT reason (not syntax/import errors)
- Only one test at a time - this is critical for TDD discipline
- Exception: For browser-level tests or expensive setup (e.g., Storybook
*.stories.tsx), group multiple assertions within a single test block to avoid redundant setup - but only when adding assertions to an existing interaction flow. If new user interactions are required, still create a new test. Split files by category if they exceed ~1000 lines.
- Exception: For browser-level tests or expensive setup (e.g., Storybook
- Adding a single test to a test file is ALWAYS allowed - no prior test output needed
- Starting TDD for a new feature is always valid, even if test output shows unrelated work
- For DOM-based tests, use
data-testidattributes to select elements rather than CSS classes, tag names, or text content - Avoid hard-coded timeouts both in form of sleep() or timeout: 5000 etc; use proper async patterns (
waitFor,findBy*, event-based sync) instead and rely on global test configs for timeout settings
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 · 123 lines · 10 tokens per session scan A 0012a93230aa
red 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,280 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to cycle, differing in 16 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.