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-status)<a href="https://agentmods.dev/commands/rizethereum/claude-code-requirements-builder/requirements-status"><img src="https://agentmods.dev/badge/commands/rizethereum/claude-code-requirements-builder/requirements-status.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.00237 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
requirements-status 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 7d 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.
What it actually says
Check Requirements Status
Show current requirement gathering progress and continue.
Instructions:
-
Read requirements/.current-requirement
-
If no active requirement:
- Show message: "No active requirement gathering"
- Suggest /requirements-start or /requirements-list
- Exit
-
If active requirement exists:
- Read metadata.json for current phase and progress
- Show formatted status
- Load appropriate question/answer files
- Continue from last unanswered question
Status Display Format:
📋 Active Requirement: [name]
Started: [time ago]
Phase: [Discovery/Detail]
Progress: [X/Y] questions answered
[Show last 3 answered questions with responses]
Next Question:
[Show next unanswered question with default]
Continuation Flow:
- Read next unanswered question from file
- Present to user with default
- Accept yes/no/idk response
- Update answer file
- Update metadata progress
- Move to next question or phase
Phase Transitions:
- Discovery complete → Run context gathering → Generate detail questions
- Detail complete → Generate final requirements spec
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.
- 7d ago First seen · 42 lines · 0 tokens per session scan A c09a65f98097
requirements-status is a command published in the GitHub repository rizethereum/claude-code-requirements-builder (1,760 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 237 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.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
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.