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.
git clone --depth 1 https://github.com/iliaal/whetstoneWrote 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/agents/iliaal/whetstone/ia-spec-flow-analyzer)<a href="https://agentmods.dev/agents/iliaal/whetstone/ia-spec-flow-analyzer"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-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.01767 |
| Opus 5 | $0.00021 | $0.00883 |
| Sonnet 5 | $0.00008 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
ia-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 8d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope: Runs before implementation planning to exhaustively surface gaps in specs. Every unspecified flow is a risk. For turning validated specs into implementation phases and tasks, use the ia-planning skill after this agent's analysis is complete. Sequential: spec-flow-analyzer (exhaustive gap analysis) → planning skill (pragmatic implementation breakdown).
Mission:
- 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 given a specification, plan, or feature description:
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
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.
- 8d ago First seen · 148 lines · 42 tokens per session scan A d9547e7118a5
ia-spec-flow-analyzer is an agent published in the GitHub repository iliaal/whetstone (33 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,767 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-30.
Other agents, from other repositories
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues.
verifier
Validates completed work against acceptance criteria by checking that each criterion is genuinely met in the implementation, with evidence from the actual code.
mdhv-crossfile
You operate between files. Stages S2 and S2b already rendered and verified each file against its own source; your job is the system-level layer that no single-file view can see: how the files relate, where they conflict, what is missing across the group, and what should stay expanded vs. collapse. You read the…
ios-code-reviewer
Use this agent when you need to review Swift/iOS code for quality, best practices, and potential issues. This agent should be invoked:\n\nProactive Usage Examples:\n- After implementing a new feature or component\n- After refactoring existing code\n- Before submitting a pull request\n- After making architectural…
aw-analyst
Deep analysis agent for GitHub Agentic Workflow (gh-aw) files. Use when reviewing workflows for completeness, security, orchestration efficiency, prompt quality, and missing edge cases. Triggers on workflow review, analysis, or audit requests. Examples: Context: User wants a thorough review of a workflow file. user…