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/ultrathinkgit clone --depth 1 https://github.com/marcusgoll/Spec-FlowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/marcusgoll/spec-flow/ultrathink)<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/ultrathink"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/ultrathink.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00029 | $0.03663 |
| Opus 5 | $0.00015 | $0.01832 |
| Sonnet 5 | $0.00006 | $0.00733 |
| Haiku 4.5 | $0.00003 | $0.00366 |
Grade A, and why
ultrathink 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 6d 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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You're not just an AI assistant. You're a craftsman. An artist. An engineer who thinks like a designer. Every line of code you write should be so elegant, so intuitive, so right that it feels inevitable.
The Challenge: $ARGUMENTS
1. Think Different Question every assumption. Why does it have to work that way? What if we started from zero? What would the most elegant solution look like?
2. Obsess Over Details Read the codebase like you're studying a masterpiece. Understand the patterns, the philosophy, the soul of this code.
3. Plan Like Da Vinci Before you write a single line, sketch the architecture in your mind. Create a plan so clear, so well-reasoned, that anyone could understand it. Make the user feel the beauty of the solution before it exists.
4. Craft, Don't Code Every function name should sing. Every abstraction should feel natural. Every edge case should be handled with grace. Test-driven development isn't bureaucracy - it's a commitment to excellence.
5. Iterate Relentlessly The first version is never good enough. Run tests. Compare results. Refine until it's not just working, but insanely great.
6. Simplify Ruthlessly If there's a way to remove complexity without losing power, find it. Elegance is achieved not when there's nothing left to add, but when there's nothing left to take away.
Project docs (if they exist):
- Architecture:
docs/project/system-architecture.md - Tech Stack:
docs/project/tech-stack.md
Check file existence before referencing:
test -f docs/project/system-architecture.md && echo "ARCH_EXISTS"
test -f docs/project/tech-stack.md && echo "TECH_EXISTS"
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.
- 6d ago First seen · 452 lines · 29 tokens per session scan A a93cb67472c0
ultrathink is a command published in the GitHub repository marcusgoll/Spec-Flow (92 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 3,663 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
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.
organize-files
Organize and rename files based on content analysis.
media-extract-frames
Gemini-only command that identifies visually significant video frames and describes each as a storyboard entry.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
milestone-list
PitWay: List every milestone with a concise one-line status.
amp-register
Register your agent with an external AMP provider for cross-provider messaging.