Borrowing it
Nothing to install: this file belongs to growilabs/growi-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/growilabs/growi-mcp-server/main/.claude/commands/kiro/spec-requirements.mdgit clone --depth 1 https://github.com/growilabs/growi-mcp-serverWrote 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/growilabs/growi-mcp-server/spec-requirements)<a href="https://agentmods.dev/commands/growilabs/growi-mcp-server/spec-requirements"><img src="https://agentmods.dev/badge/commands/growilabs/growi-mcp-server/spec-requirements/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/growilabs/growi-mcp-server/spec-requirements"><img src="https://agentmods.dev/badge/commands/growilabs/growi-mcp-server/spec-requirements.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.00006 | $0.00399 |
| Opus 5 | $0.00003 | $0.00199 |
| Sonnet 5 | $0.00001 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
spec-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 9d 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
Requirements Generation
Parse Arguments
- Feature name:
$1
Validate
Check that spec has been initialized:
- Verify
.kiro/specs/$1/exists - Verify
.kiro/specs/$1/spec.jsonexists
If validation fails, inform user to run /kiro:spec-init first.
Invoke Subagent
Delegate requirements generation to spec-requirements-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="spec-requirements-agent",
description="Generate EARS requirements",
prompt="""
Feature: $1
Spec directory: .kiro/specs/$1/
File patterns to read:
- .kiro/specs/$1/spec.json
- .kiro/specs/$1/requirements.md
- .kiro/steering/*.md
- .kiro/settings/rules/ears-format.md
- .kiro/settings/templates/specs/requirements.md
Mode: generate
"""
)
Display Result
Show Subagent summary to user, then provide next step guidance:
Next Phase: Design Generation
If Requirements Approved:
- Review generated requirements at
.kiro/specs/$1/requirements.md - Optional Gap Analysis (for existing codebases):
- Run
/kiro:validate-gap $1to analyze implementation gap with current code - Identifies existing components, integration points, and implementation strategy
- Recommended for brownfield projects; skip for greenfield
- Run
- Then
/kiro:spec-design $1 [-y]to proceed to design phase
If Modifications Needed:
- Provide feedback and re-run
/kiro:spec-requirements $1
Note: Approval is mandatory before proceeding to design phase.
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.
- 9d ago First seen · 63 lines · 6 tokens per session scan A df2d7fb75d50
spec-requirements is a command published in the GitHub repository growilabs/growi-mcp-server (19 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 399 once invoked, about $0.0000 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
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.