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/gategit 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.00012 | $0.03643 |
| Opus 5 | $0.00006 | $0.01821 |
| Sonnet 5 | $0.00002 | $0.00729 |
| Haiku 4.5 | $0.00001 | $0.00364 |
Grade A, and why
gate 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 — 604 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gate — Quality Gates
Current Branch: !git branch --show-current 2>/dev/null || echo "none"
Project Detection:
- Node.js: !
test -f package.json && echo "yes" || echo "no" - Python: !
test -f pyproject.toml -o -f requirements.txt && echo "yes" || echo "no" - Rust: !
test -f Cargo.toml && echo "yes" || echo "no" - Go: !
test -f go.mod && echo "yes" || echo "no"
Workflow State: @.spec-flow/memory/state.yaml
| Command | Purpose | Pass Criteria |
|---|---|---|
/gate ci |
CI quality checks | All checks pass |
/gate sec |
Security scanning | No CRITICAL/HIGH issues |
Gates block deployment until passed.
Step 1: Parse Gate Type
Extract first argument as gate type:
ci→ Run CI quality checkssec→ Run security scanning
If no argument provided, use AskUserQuestion:
{
"questions": [{
"question": "Which quality gate do you want to run?",
"header": "Gate",
"multiSelect": false,
"options": [
{"label": "ci", "description": "Tests, linting, types, coverage (Recommended)"},
{"label": "sec", "description": "SAST, secrets detection, dependency audit"}
]
}]
}
Gate: CI (/gate ci)
Purpose
Validate code quality before deployment:
- All tests pass
- Linting checks pass
- Type checks pass
- Coverage meets threshold (if configured)
Step CI-1: Detect Project Type
Use Glob to detect project files:
| File Found | Project Type | Test Command | Lint Command | Type Command |
|---|---|---|---|---|
package.json |
Node.js | npm test or pnpm test |
npm run lint |
npx tsc --noEmit |
pyproject.toml |
Python | pytest |
ruff check . |
mypy . |
Cargo.toml |
Rust | cargo test |
cargo clippy |
cargo check |
go.mod |
Go | go test ./... |
go vet ./... |
(included in vet) |
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 · 604 lines · 0 tokens per session scan A 00a85aabfb2d
gate is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 3,643 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
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.