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/marcusgoll/spec-flow/validategit clone --depth 1 https://github.com/marcusgoll/Spec-FlowWhat 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.00033 | $0.02531 |
| Opus 5 | $0.00016 | $0.01265 |
| Sonnet 5 | $0.00007 | $0.00506 |
| Haiku 4.5 | $0.00003 | $0.00253 |
Grade A, and why
validate 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Current workflow state: Auto-detected from ${BASE_DIR}/*/state.yaml
Feature spec exists: Auto-detected (epics//epic-spec.md OR specs//spec.md)
Plan exists: Auto-detected (epics//plan.md OR specs//plan.md)
Tasks exist: Auto-detected (epics//tasks.md OR specs//tasks.md)
Engineering Principles: !test -f docs/project/engineering-principles.md && echo "✅ Found" || echo "❌ Missing (run /init-project)"
Previous validation: Auto-detected from ${BASE_DIR}/*/analysis-report.md
Analyzes:
- Spec ↔ Plan ↔ Tasks consistency
- Constitution compliance (8 engineering principles)
- Breaking changes (API, schema, env vars)
- Test coverage completeness
- Implementation readiness
Outputs:
- analysis-report.md with CRITICAL/MAJOR/MINOR findings
- Recommendation: PROCEED | FIX_CRITICAL | FIX_ALL
Operating constraints:
- STRICTLY READ-ONLY — Never modify spec, plan, or tasks files
- Constitution Authority — Constitution violations auto-CRITICAL
- Token Efficient — Max 50 findings, aggregate overflow
- Deterministic — Consistent finding IDs across runs
Dependencies:
- Git repository initialized
- spec.md, plan.md, tasks.md completed
- Optional: docs/project/engineering-principles.md for principle validation
Step 0: WORKFLOW DETECTION
Detect workflow using centralized skill (see .claude/skills/workflow-detection/SKILL.md):
- Run detection:
bash .spec-flow/scripts/utils/detect-workflow-paths.sh - Parse JSON: Extract
type,base_dir,slugfrom output - If detection fails (exit code != 0): Use AskUserQuestion fallback
- Set paths:
- Feature:
SPEC_FILE="${BASE_DIR}/${SLUG}/spec.md" - Epic:
SPEC_FILE="${BASE_DIR}/${SLUG}/epic-spec.md" - Common:
PLAN_FILE,TASKS_FILE,REPORT_FILEall in${BASE_DIR}/${SLUG}/
- Feature:
Fallback prompt (if detection fails):
- Question: "Which workflow are you working on?"
- Options: "Feature" (specs/), "Epic" (epics/)
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 · 308 lines · 0 tokens per session scan A 7ab72513b412
validate is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 2,531 once invoked, about $0.0002 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
quick-fix
Fast-track workflow for small bug fixes.
review
Review the current diff for violations of the conventions in AGENTS.md and .cursor/rules/. Report findings ordered by severity; do not fix anything unless asked.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.
milestone-list
PitWay: List every milestone with a concise one-line status.
setup
Install the claude-pace statusline bundled with this plugin.