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.
git clone --depth 1 https://github.com/rizethereum/claude-code-requirements-builderWrote 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/rizethereum/claude-code-requirements-builder/requirements-current)<a href="https://agentmods.dev/commands/rizethereum/claude-code-requirements-builder/requirements-current"><img src="https://agentmods.dev/badge/commands/rizethereum/claude-code-requirements-builder/requirements-current/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rizethereum/claude-code-requirements-builder/requirements-current"><img src="https://agentmods.dev/badge/commands/rizethereum/claude-code-requirements-builder/requirements-current.svg" alt="Reviewed on agentmods" width="80" 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.00555 |
| Opus 5.5 | $0.00000 | $0.00222 |
| Sonnet 5.5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
requirements-current 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
View Current Requirement
Display detailed information about the active requirement.
Instructions:
-
Read requirements/.current-requirement
-
If no active requirement:
- Show "No active requirement"
- Display last 3 completed requirements
- Exit
-
For active requirement:
- Load all files from requirement folder
- Display comprehensive status
- Show codebase analysis overview
- Show all questions and answers so far
- Display context findings if available
- Indicate current phase and next steps
File Structure:
- 00-initial-request.md - Original user request
- 01-discovery-questions.md - Context discovery questions
- 02-discovery-answers.md - User's answers
- 03-context-findings.md - AI's codebase analysis
- 04-detail-questions.md - Expert requirements questions
- 05-detail-answers.md - User's detailed answers
- 06-requirements-spec.md - Final requirements document
Display Format:
📋 Current Requirement: [name]
⏱️ Duration: [time since start]
📊 Phase: [Initial Setup/Context Discovery/Targeted Context/Expert Requirements/Complete]
🎯 Progress: [total answered]/[total questions]
📄 Initial Request:
[Show content from 00-initial-request.md]
🏗️ Codebase Overview (Phase 1):
- Architecture: [e.g., React + Node.js + PostgreSQL]
- Main components: [identified services/modules]
- Key patterns: [discovered conventions]
✅ Context Discovery Phase (5/5 complete):
Q1: Will users interact through a visual interface? YES
Q2: Does this need to work on mobile? YES
Q3: Will this handle sensitive data? NO
Q4: Do users have a current workaround? YES (default)
Q5: Will this need offline support? IDK → NO (default)
🔍 Targeted Context Findings:
- Specific files identified: [list key files]
- Similar feature: UserProfile at components/UserProfile.tsx
- Integration points: AuthService, ValidationService
- Technical constraints: Rate limiting required
🎯 Expert Requirements Phase (2/8 answered):
Q1: Use existing ValidationService at services/validation.ts? YES
Q2: Extend UserModel at models/User.ts? YES
Q3: Add new API endpoint to routes/api/v1? [PENDING]
...
📝 Next Action:
- Continue with /requirements-status
- End early with /requirements-end
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.
- 1mo ago First seen · 72 lines · 0 tokens per session scan A a6501ef7fde7
requirements-current is a command published in the GitHub repository rizethereum/claude-code-requirements-builder (1,759 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 555 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.