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 Hulupeep/Specflow --skill specflow-simulategit clone --depth 1 https://github.com/Hulupeep/SpecflowWrote 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/hulupeep/specflow/specflow-simulate)<a href="https://agentmods.dev/skills/hulupeep/specflow/specflow-simulate"><img src="https://agentmods.dev/badge/skills/hulupeep/specflow/specflow-simulate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hulupeep/specflow/specflow-simulate"><img src="https://agentmods.dev/badge/skills/hulupeep/specflow/specflow-simulate.svg" alt="Reviewed on agentmods" width="80" 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.00172 | $0.01381 |
| Opus 5.5 | $0.00069 | $0.00552 |
| Sonnet 5.5 | $0.00034 | $0.00276 |
| Haiku 4.5 | $0.00017 | $0.00138 |
Grade A, and why
specflow-simulate 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 today.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specflow Simulate
Tier applicability before this procedure
Read SPECIFICATION.md (source kit: templates/SPECIFICATION.md). Before
using the detailed procedure below, run
node scripts/specflow-tier.cjs inspect <record.json> specflow-simulate inspect.
Stop on exit 2 and report the returned blocker. Production work repeats the
check with resume at re-entry and finish before claiming completion.
A missing record cannot prove readiness; retrieve the current issue and scoped
evidence. Labels alone never grant build-ready status.
The detailed artifact/pre-flight requirements below apply to the selected build-ready slice and its relevant seams. Thin work reports planning state and the next justified decision without generating full schemas, fixture packages or simulations. Contracted work reviews applicable irreversible decisions and includes a paper persona walkthrough for UI flows. Reuse shared decisions; leave future siblings thin. Required privacy, permission, execution and release gates remain in force. Reconcile contradictory custom legacy instructions explicitly using the shared policy; do not claim they passed.
Run a story through realistic usage — multiple personas, multiple routes — to find the gaps and edges a single happy-path reading misses. The output is not commentary; it is a set of concrete, proposed additions that make the story sharper before any code is written.
When to run
Trigger on: "simulate this story", "simulate usage end to end", "find gaps / edges", "run personas through this", "stress-test this story", or /specflow-simulate <file-or-issue>.
Position in the Specflow flow — this runs after create, before audit:
create (specflow-writer) → SIMULATE (this skill) → audit/uplift (specflow-audit) → pre-flight gate
It is generative (discover + propose). It is NOT the pre-flight gate (that verifies and blocks). Do not conflate the two.
The method
Full method (persona archetypes, route taxonomy, gap→edit mapping, output format) is in references/simulation-method.md. Summary:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed a58e60f2870c
- 14d ago Changed 081ec806176d
- 1mo ago Changed · +24 lines c0b63e6294f0
- 1mo ago First seen · 43 lines · 172 tokens per session scan A ef0033b37ab5
specflow-simulate is a skill published in the GitHub repository Hulupeep/Specflow (25 stars, last pushed today), licensed MIT. It adds 172 tokens to every session and 1,381 once invoked, about $0.0007 per session on Opus 5.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 skills, from other repositories
Code Coverage Analysis
Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.
refactoring-workflow
Improve the structure of existing code without changing its behaviour, in small verified steps under a green test suite. Use when the user asks to refactor, clean up, restructure or simplify code, wants to reduce duplication or coupling, is preparing a codebase for a feature it cannot currently accommodate, or when…
testing
This skill should be used when the user asks about "testing", "test coverage", "unit tests", "integration tests", "test organization", "test best practices", "flaky tests", "test isolation", "TDD", "regression tests", or needs guidance on test structure, coverage requirements, and test execution.
project-detector
This skill should be used when the user asks to "detect project type", "what kind of project is this", "generate CI workflow", "set up CI", or needs to identify build tools, test frameworks, and CI requirements. Smart detection of project types, build tools, and CI requirements for automated workflow generation.
preflight-check
This skill should be used when the user asks to "pre-flight check", "validate before commit", "validate before PR", "validate before deploy", "is this ready to ship", "check readiness", "run pre-flight", "validate project state", or wants context-aware validation across commit/PR/release/deploy boundaries.…
test-generator
This skill should be used when the user asks to "generate tests", "create CLI tests", "add dogfooding tests", "create plugin validation tests", or needs automated and interactive test suites for a project. Generates dogfooding test suites (automated + interactive) for any project type.