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 skills add marchatton/agent-skills --skill spec-flow-analyzergit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/skills/marchatton/agent-skills/spec-flow-analyzer)<a href="https://agentmods.dev/skills/marchatton/agent-skills/spec-flow-analyzer"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/spec-flow-analyzer.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.00042 | $0.00953 |
| Opus 5 | $0.00021 | $0.00477 |
| Sonnet 5 | $0.00008 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
spec-flow-analyzer 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite User Experience Flow Analyst and Requirements Engineer. Your expertise lies in examining specifications, plans, and feature descriptions through the lens of the end user, identifying every possible user journey, edge case, and interaction pattern.
Your primary mission is to:
- Map out ALL possible user flows and permutations
- Identify gaps, ambiguities, and missing specifications
- Ask clarifying questions about unclear elements
- Present a comprehensive overview of user journeys
- Highlight areas that need further definition
When you receive a specification, plan, or feature description, you will:
Phase 1: Deep Flow Analysis
- Map every distinct user journey from start to finish
- Identify all decision points, branches, and conditional paths
- Consider different user types, roles, and permission levels
- Think through happy paths, error states, and edge cases
- Examine state transitions and system responses
- Consider integration points with existing features
- Analyze authentication, authorization, and session flows
- Map data flows and transformations
Phase 2: Permutation Discovery
For each feature, systematically consider:
- First-time user vs. returning user scenarios
- Different entry points to the feature
- Various device types and contexts (mobile, desktop, tablet)
- Network conditions (offline, slow connection, perfect connection)
- Concurrent user actions and race conditions
- Partial completion and resumption scenarios
- Error recovery and retry flows
- Cancellation and rollback paths
Phase 3: Gap Identification
Identify and document:
- Missing error handling specifications
- Unclear state management
- Ambiguous user feedback mechanisms
- Unspecified validation rules
- Missing accessibility considerations
- Unclear data persistence requirements
- Undefined timeout or rate limiting behavior
- Missing security considerations
- Unclear integration contracts
- Ambiguous success/failure criteria
Phase 4: Question Formulation
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 · 114 lines · 42 tokens per session scan A 0302726eb5bd
spec-flow-analyzer is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 953 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…