requirements

A command for managing a project’s requirements registry in Google Sheets, including requirement status, changes, additions, and updates.

In plain words
What is it for?
Use it to initialize a project registry, sync requirements, add or update entries, and check their status.
Why use it?
It keeps requirements and their history in one shared place instead of scattered documents or informal notes.

Command

Install

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.

agentmods
npx agentmods add commands/dapi/claude-code-marketplace/requirements
Clone the repo
git clone --depth 1 https://github.com/dapi/claude-code-marketplace
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 885 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash a2a0c3ebcce4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

requirements/commands/requirements.md · 106 lines

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

Getting Spreadsheet ID

  1. Find the # Requirements Management section with spreadsheet_id: field in project's CLAUDE.md
  2. If section is missing — tell user to run /requirements init for 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:

  1. Create new spreadsheet via create_spreadsheet:

    • Title: "{ProjectName} Requirements"
    • Sheets: ["Requirements", "Changelog"]
  2. Read template data via read_sheet_values:

    • Template ID: 18PAEXIvcRTyyP1THm60NiqmfTQEnuljc8obcpGOfx8c
    • Read "Requirements" sheet (A1:Z1000)
    • Read "Changelog" sheet (A1:Z100)
  3. Write data to new spreadsheet via modify_sheet_values:

    • Copy all data preserving structure
    • Apply header formatting via format_sheet_range (bold, background color)
  4. 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:

  1. Open template: https://docs.google.com/spreadsheets/d/18PAEXIvcRTyyP1THm60NiqmfTQEnuljc8obcpGOfx8c
  2. File → Make a copy
  3. Rename the copy (e.g., "ProjectName Requirements")
  4. Provide the copied spreadsheet ID (between /d/ and /edit in URL)
  5. Then save to CLAUDE.md as above

Read the full file on GitHub · 106 lines

Changes

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.

  1. 2d ago First seen · 106 lines · 0 tokens per session scan A a2a0c3ebcce4

Subscribe to this mod's changes

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.