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/marcelsud/spec-driven-agentic-development/reviewgit clone --depth 1 https://github.com/marcelsud/spec-driven-agentic-developmentWhat 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.01845 |
| Opus 5 | $0.00006 | $0.00923 |
| Sonnet 5 | $0.00003 | $0.00369 |
| Haiku 4.5 | $0.00001 | $0.00185 |
Grade A, and why
review 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Feature Specification
Review a feature specification for completeness, EARS format compliance, and identify areas for improvement.
Feature: $ARGUMENTS
Feature Selection
-
IF a feature name is provided in
$ARGUMENTS:- Find a directory in
features/that matches$ARGUMENTS - If no exact match, search for closest match and ask for confirmation
- Find a directory in
-
IF no feature name is provided:
- List all directories under
features/ - If only one exists, select it automatically
- If multiple exist, ask user to specify using
AskUserQuestion
- List all directories under
Your Task
Analyze the feature specification files and produce a comprehensive quality review.
Process
Step 1: Load Feature Files
Read all specification files:
features/[feature-name]/context.mdfeatures/[feature-name]/requirements.mdfeatures/[feature-name]/tasks.md
If any file is missing, note it as a critical issue.
Step 2: Review context.md
Check for required sections:
- Overview - Brief description of the feature
- Goals - What the feature aims to achieve
- Scope - In Scope / Out of Scope clearly defined
- Technical Decisions - Stack, architecture, key decisions with rationale
- Constraints & Considerations - Limitations and important factors
- Dependencies - External dependencies and requirements
Flag as issues:
- Missing sections (Critical)
- Empty or placeholder content (Warning)
- Technical decisions without rationale (Suggestion)
Step 3: Review requirements.md - EARS Compliance
Check EARS Format
Each requirement must use one of these patterns:
| Type | Pattern | Example |
|---|---|---|
| Ubiquitous | "The system SHALL [requirement]" | The system SHALL encrypt all passwords |
| Event-Driven | "WHEN [trigger] THEN the system SHALL [response]" | WHEN user clicks submit THEN the system SHALL validate input |
| State-Driven | "WHILE [state] the system SHALL [requirement]" | WHILE processing payment the system SHALL display progress |
| Conditional | "IF [condition] THEN the system SHALL [requirement]" | IF cart is empty THEN the system SHALL show empty message |
| Optional | "WHERE [feature] the system SHALL [requirement]" | WHERE premium enabled the system SHALL allow exports |
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 · 232 lines · 13 tokens per session scan A e6e5d3995c03
review is a command published in the GitHub repository marcelsud/spec-driven-agentic-development (174 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 1,845 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
git
Git operations with intelligent commit messages and workflow optimization.
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.