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/rizethereum/claude-code-requirements-builder/requirements-endgit 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-end)<a href="https://agentmods.dev/commands/rizethereum/claude-code-requirements-builder/requirements-end"><img src="https://agentmods.dev/badge/commands/rizethereum/claude-code-requirements-builder/requirements-end.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.00373 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
requirements-end 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 6d 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
End Requirements Gathering
Finalize the current requirement gathering session.
Instructions:
-
Read requirements/.current-requirement
-
If no active requirement:
- Show "No active requirement to end"
- Exit
-
Show current status and ask user intent:
⚠️ Ending requirement: [name] Current phase: [phase] ([X/Y] complete) What would you like to do? 1. Generate spec with current information 2. Mark as incomplete for later 3. Cancel and delete -
Based on choice:
Option 1: Generate Spec
- Create 06-requirements-spec.md
- Include all answered questions
- Add defaults for unanswered with "ASSUMED:" prefix
- Generate implementation hints
- Update metadata status to "complete"
Option 2: Mark Incomplete
- Update metadata status to "incomplete"
- Add "lastUpdated" timestamp
- Create summary of progress
- Note what's still needed
Option 3: Cancel
- Confirm deletion
- Remove requirement folder
- Clear .current-requirement
Final Spec Format:
# Requirements Specification: [Name]
Generated: [timestamp]
Status: [Complete with X assumptions / Partial]
## Overview
[Problem statement and solution summary]
## Detailed Requirements
### Functional Requirements
[Based on answered questions]
### Technical Requirements
- Affected files: [list with paths]
- New components: [if any]
- Database changes: [if any]
### Assumptions
[List any defaults used for unanswered questions]
### Implementation Notes
[Specific guidance for implementation]
### Acceptance Criteria
[Testable criteria for completion]
- Clear .current-requirement
- Update requirements/index.md
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.
- 6d ago First seen · 74 lines · 0 tokens per session scan A 5cbee15e6ac5
requirements-end 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 373 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
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.