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 skills/ajelinek/specflow/901-feature-loopnpx skills add ajelinek/SpecFlow --skill 901-feature-loopgit clone --depth 1 https://github.com/ajelinek/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/ajelinek/specflow/901-feature-loop)<a href="https://agentmods.dev/skills/ajelinek/specflow/901-feature-loop"><img src="https://agentmods.dev/badge/skills/ajelinek/specflow/901-feature-loop.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 | $0.00160 | $0.06291 |
| Opus 5 | $0.00080 | $0.03145 |
| Sonnet 5 | $0.00032 | $0.01258 |
| Haiku 4.5 | $0.00016 | $0.00629 |
Grade A, and why
901-feature-loop 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 423 lines · 160 tokens per session scan A 2e5cb826809b
901-feature-loop is a skill published in the GitHub repository ajelinek/SpecFlow (11 stars, last pushed 7d ago), with no licence file. It adds 160 tokens to every session and 6,291 once invoked, about $0.0008 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 skills, from other repositories
implement-slice
Implement the next smallest slice from the current plan using TDD — tests first, then code, then verification, then an atomic commit. Reads the plan from the scratchpad.
invokta-delivery
Deliver Invokta milestones and work items with TDD, adherence to versioned contracts and architecture, complete validation, and one cohesive commit per work item. Use when developing features, fixing bugs, executing roadmap milestones, or completing acceptance criteria in this repository.
ai-build
Executes one task of an already approved plan, red to green to refactor, as one logical change with a clean checkpoint that says nobody has reviewed it yet. Trigger for "implement task 3", "build this", "make the plan's next step work", "write the code for this spec". Not for deciding what to build — use /ai-spec…
wf-quick
Malý task bez kontraktu — 1–3 akceptační kritéria v chatu, TDD v aktuální session, risk-based review, vždy branch + draft PR a explain dokument. Použij pro drobné fixy a malé featury; větší nebo rizikové tasky eskaluje na /wf.
gh-issue
Fetch a GitHub issue, create a branch, implement with TDD, and open a PR.
sdlc-tdd
A Single Cycle of TDD (Red-Green Phases). Reviews the provided implementation plan, and Test case, implements the next test in Red-Green, Commit cycle.