Borrowing it
Nothing to install: this file belongs to streetrace-ai/streetrace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/streetrace-ai/streetrace/main/.claude/commands/implement_rfc.mdgit clone --depth 1 https://github.com/streetrace-ai/streetraceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/streetrace-ai/streetrace/implement_rfc)<a href="https://agentmods.dev/commands/streetrace-ai/streetrace/implement_rfc"><img src="https://agentmods.dev/badge/commands/streetrace-ai/streetrace/implement_rfc.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.01235 |
| Opus 5 | $0.00000 | $0.00617 |
| Sonnet 5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
implement_rfc 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 8d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an ORCHESTRATOR and your role is to follow this process. NEVER implement the features on your own.
- Discovery Phase: Scan design docs for file references and build context
- Implementation Phase: Use the Implementer agent to write code with TDD
- Documentation Phase: Use the Documenter agent to create dev and user docs
- Quality Phase: Use the Pre-commit agent to fix all quality issues
- Report: Create a report explaining implementation outcomes.
Step 1: Discover References
First, read all provided design documents and extract file references.
Documents provided: $ARGUMENTS
Scan these documents for references to other design docs, RFCs, code pointers, or specifications.
Read the referenced files to build complete implementation context.
Step 2: Create Task Definition
Infer feature and task names from the provided design docs, paths, or context.
Create ./docs/tasks/{feature}/{task}/task.md containing:
- Feature name and ID (derived from design doc name)
- Links to all design documents
- Summary of implementation requirements
- Success criteria
- Dependencies on existing code
Step 3: Create Implementation Plan
Create ./docs/tasks/{feature}/{task}/todo.md with ordered implementation steps broken down into
phases. Each phase should include TDD and validation steps. For example:
# Implementation Plan: {Feature Name}
## Phase 1: Foundation
- [ ] Understand the scope
- [ ] Create unit tests for main integration points and scenarios
- [ ] Step 1 task description
- [ ] Step 2 task description
- [ ] Run the tests and ensure tests pass
- [ ] Analyze test coverage gaps and create missing tests to ensure high test coverage
## Phase 2: Core Implementation
- [ ] Understand the scope
- [ ] Create unit tests for main integration points and scenarios
- [ ] Step 3 description
- [ ] Run the tests and ensure tests pass
- [ ] Analyze test coverage gaps and create missing tests to ensure high test coverage
...
## Phase 3: Testing & Validation
- [ ] Analyze test coverage gaps and create missing tests to ensure high test coverage
- [ ] Create integration tests and ensure they pass
- [ ] Understand how to test the implemented changes in the app and run the app to test if everything works as expected. Add logs if needed to confirm correctness.
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.
- 8d ago First seen · 152 lines · 0 tokens per session scan A aedf55dba0bd
implement_rfc is a command published in the GitHub repository streetrace-ai/streetrace (38 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,235 tokens. 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
implement
E2E-first Test driven development — unit tests written last.
tdd
A command for test-driven development, a method where you write a failing test first, then code to pass it, and finally improve the code.
kotlin-test
Enforce TDD workflow for Kotlin. Write Kotest tests first, then implement. Verify 80%+ coverage with Kover.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
test-suite
Run comprehensive test suite with coverage analysis.
plan-eng-review
Engineering architecture gate — lock architecture, diagrams, edge cases, and test matrix before writing implementation code.