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/dapi/claude-code-marketplace/requirementsgit clone --depth 1 https://github.com/dapi/claude-code-marketplaceWhat 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 | $0.00013 | $0.00885 |
| Opus 5 | $0.00006 | $0.00443 |
| Sonnet 5 | $0.00003 | $0.00177 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
requirements 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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Manager
Manage project requirements registry via Google Spreadsheet.
Configuration
- Template: https://docs.google.com/spreadsheets/d/18PAEXIvcRTyyP1THm60NiqmfTQEnuljc8obcpGOfx8c
- Google Email: [email protected]
Getting Spreadsheet ID
- Find the
# Requirements Managementsection withspreadsheet_id:field in project's CLAUDE.md - If section is missing — tell user to run
/requirements initfor initialization
Command: $ARGUMENTS
Execute action based on argument:
If init
Step 1: Determine project name
- Extract from
git remote get-url origin(repo name) - Or use current directory name as fallback
Step 2: Automatically create spreadsheet copy
Try to create a copy programmatically using Google Workspace MCP:
-
Create new spreadsheet via
create_spreadsheet:- Title: "{ProjectName} Requirements"
- Sheets: ["Requirements", "Changelog"]
-
Read template data via
read_sheet_values:- Template ID:
18PAEXIvcRTyyP1THm60NiqmfTQEnuljc8obcpGOfx8c - Read "Requirements" sheet (A1:Z1000)
- Read "Changelog" sheet (A1:Z100)
- Template ID:
-
Write data to new spreadsheet via
modify_sheet_values:- Copy all data preserving structure
- Apply header formatting via
format_sheet_range(bold, background color)
-
Share spreadsheet via
share_drive_file:- Share with user's email as owner (already owner by default)
Step 3: On success
- Save to project's CLAUDE.md:
# Requirements Management - **spreadsheet_id:** <NEW_ID> - **spreadsheet_url:** https://docs.google.com/spreadsheets/d/<NEW_ID> - Show success message with link to new spreadsheet
Step 4: On failure (fallback to manual)
If automatic creation fails, instruct the user:
- Open template: https://docs.google.com/spreadsheets/d/18PAEXIvcRTyyP1THm60NiqmfTQEnuljc8obcpGOfx8c
- File → Make a copy
- Rename the copy (e.g., "ProjectName Requirements")
- Provide the copied spreadsheet ID (between
/d/and/editin URL) - Then save to CLAUDE.md as above
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.
- 2d ago First seen · 106 lines · 0 tokens per session scan A a2a0c3ebcce4
requirements is a command published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 885 once invoked, about $0.0001 per session on Opus 5. 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.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).