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-list)<a href="https://agentmods.dev/commands/rizethereum/claude-code-requirements-builder/requirements-list"><img src="https://agentmods.dev/badge/commands/rizethereum/claude-code-requirements-builder/requirements-list/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-list"><img src="https://agentmods.dev/badge/commands/rizethereum/claude-code-requirements-builder/requirements-list.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.00399 |
| Opus 5.5 | $0.00000 | $0.00160 |
| Sonnet 5.5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
requirements-list 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.
What it actually says
List All Requirements
Display all requirements with their status and summaries.
Instructions:
-
Check requirements/.current-requirement for active requirement
-
List all folders in requirements/ directory
-
For each requirement folder:
- Read metadata.json
- Extract key information
- Format for display
-
Sort by:
- Active first (if any)
- Then by status: complete, incomplete
- Then by date (newest first)
Display Format:
📚 Requirements Documentation
🔴 ACTIVE: profile-picture-upload
Phase: Discovery (3/5) | Started: 30m ago
Next: Q4 about file restrictions
✅ COMPLETE:
2025-01-26-0900-dark-mode-toggle
Status: Ready for implementation | 15 questions answered
Summary: Full theme system with user preferences
Linked PR: #234 (merged)
2025-01-25-1400-export-reports
Status: Implemented | 22 questions answered
Summary: PDF/CSV export with filtering
⚠️ INCOMPLETE:
2025-01-24-1100-notification-system
Status: Paused at Detail phase (2/8) | Last: 2 days ago
Summary: Email/push notifications for events
📈 Statistics:
- Total: 4 requirements
- Complete: 2 (13 avg questions)
- Active: 1
- Incomplete: 1
Additional Features:
-
Show linked artifacts:
- Development sessions
- Pull requests
- Implementation status
-
Highlight stale requirements:
- Mark if incomplete > 7 days
- Suggest resuming or ending
-
Quick actions:
- "View details: /requirements-show [id]"
- "Resume incomplete: /requirements-status"
- "Start new: /requirements-start [description]"
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 · 63 lines · 0 tokens per session scan A 2ac79f0ad752
requirements-list 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 399 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.