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/validate-staginggit 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.00025 | $0.03958 |
| Opus 5 | $0.00013 | $0.01979 |
| Sonnet 5 | $0.00005 | $0.00792 |
| Haiku 4.5 | $0.00003 | $0.00396 |
Grade A, and why
validate-staging scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Test marketing health: `curl https://staging.{domain}.com/health` How it starts
The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate-staging — Staging Validation (Thin Wrapper)
v11.0 Architecture: This command spawns the isolated
validate-phase-agentvia Task(). Validation checks run in isolated context with question batching for manual verification.
Active Feature: !ls -td specs/[0-9]*-* 2>/dev/null | head -1 || echo "none"
Interaction State: !cat specs/*/interaction-state.yaml 2>/dev/null | head -10 || echo "none"
Architecture (v11.0 - Phase Isolation):
/validate-staging → Task(validate-phase-agent) → Q&A for manual checks → validation-report.md
Agent responsibilities:
- Review E2E test results from GitHub Actions
- Review Lighthouse CI performance results
- Test rollback capability
- Generate manual testing checklist from spec.md
- Return questions for user to manually verify in browser
- Create staging-validation-report.md
Operating constraints:
- Manual Gate — Agent returns questions for human validation
- Staging Environment — Validates staging URLs
- Blocking Conditions — E2E failures or manual failures block production
Workflow position: implement → optimize → validate → ship → finalize
Legacy Context (for agent reference)
<legacy_context>
Latest staging deployment: !gh run list --workflow=deploy-staging.yml --branch=main --limit=1 --json databaseId,headSha,conclusion,status,createdAt,displayTitle 2>/dev/null || echo "[]"
Vercel CLI installed: !command -v vercel >/dev/null 2>&1 && echo "✅ Yes" || echo "❌ No"
GitHub CLI authenticated: !gh auth status >/dev/null 2>&1 && echo "✅ Yes" || echo "❌ No"
</legacy_context>
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 · 479 lines · 0 tokens per session scan A 59a943d882bc
validate-staging is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 3,958 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.