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/init-preferencesgit 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.00015 | $0.05809 |
| Opus 5 | $0.00008 | $0.02905 |
| Sonnet 5 | $0.00003 | $0.01162 |
| Haiku 4.5 | $0.00002 | $0.00581 |
Grade A, and why
init-preferences 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 — 848 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What it configures:
- Command default modes (/epic, /tasks, /init-project, /run-prompt)
- UI preferences (usage stats, last-used recommendations)
- Automation behavior (CI/CD defaults)
- Git worktree preferences (parallel development)
- Prototype workflow preferences
- E2E and visual regression testing (v10.4)
- Database migration safety (v10.5)
- Perpetual learning system
Output:
- Creates/updates
.spec-flow/config/user-preferences.yaml - Provides configuration summary
- Shows example commands using new preferences
Flags:
--reset: Reset all preferences to defaults (interactive confirmation)
If $ARGUMENTS contains "--reset":
-
Read existing preferences to show what will be reset
-
Use AskUserQuestion to confirm:
Question: "Reset all preferences to defaults?" Options: - "Yes, reset everything" - All preferences will be set to defaults - "No, keep current preferences" - Cancel reset operation -
If confirmed:
- Copy
.spec-flow/config/user-preferences.example.yamlto.spec-flow/config/user-preferences.yaml - Display: "✓ Preferences reset to defaults"
- End command
- Copy
-
If cancelled: End command
Step 1: Welcome and Introduction
Display welcome message:
╔════════════════════════════════════════════════════════════════╗
║ Spec-Flow Preference Configuration Wizard ║
╚════════════════════════════════════════════════════════════════╝
This wizard will help you configure default behavior for Spec-Flow commands.
Your preferences are saved to: .spec-flow/config/user-preferences.yaml
You can always:
- Re-run this wizard to update preferences
- Edit the config file directly
- Override preferences with command-line flags
- Reset with: /init-preferences --reset
Let's get started! 🚀
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 · 848 lines · 0 tokens per session scan A f639db874517
init-preferences is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 5,809 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
sync-linear
Sync current work with Linear ticket status.
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.
auto-run
PitWay: Manage auto-run authorization for automatic task continuation.
task-integrate
PitWay: Apply a dispatched task's worktree commit to the main tree.
milestone-list
PitWay: List every milestone with a concise one-line status.
setup
Install the claude-pace statusline bundled with this plugin.