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/initgit 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.00011 | $0.00469 |
| Opus 5 | $0.00005 | $0.00234 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
init 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.
What it actually says
/init — Consolidated Project Initialization
/init→ Project documentation (8 docs via interactive questionnaire)/init --preferences→ User preference configuration/init --tokens→ Design token generation (OKLCH + WCAG)
All flags are passed through to the underlying commands.
Step 1: Parse Arguments and Route
Check $ARGUMENTS for routing:
-
If
--preferencesflag present:Extract: Remove --preferences from arguments Route to: /project/init-preferences $remaining_args -
If
--tokensflag present:Extract: Remove --tokens from arguments Route to: /project/init-tokens $remaining_args -
Otherwise (default):
Route to: /project/init-project $ARGUMENTS
Step 2: Execute Routed Command
Use SlashCommand tool to invoke the appropriate active command with all arguments passed through.
For preferences:
SlashCommand: /project/init-preferences [remaining args]
For tokens:
SlashCommand: /project/init-tokens [remaining args]
For project (default):
SlashCommand: /project/init-project [all args]
<success_criteria>
- Correct command identified from flags
- All arguments passed through properly
- Underlying command executes successfully </success_criteria>
Quick Reference
| Command | Purpose |
|---|---|
/init |
Generate 8 project docs (interactive) |
/init --preferences |
Configure command defaults |
/init --tokens |
Generate OKLCH design tokens |
/init --with-design |
Project docs + design system |
/init --ci |
Non-interactive mode for CI/CD |
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 · 85 lines · 11 tokens per session scan A 422dc9098050
init is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 469 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.