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 agents/hulupeep/specflow/workflowgit clone --depth 1 https://github.com/Hulupeep/SpecflowWhat 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.00000 | $0.03154 |
| Opus 5 | $0.00000 | $0.01577 |
| Sonnet 5 | $0.00000 | $0.00631 |
| Haiku 4.5 | $0.00000 | $0.00315 |
Grade A, and why
WORKFLOW 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 2d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specflow Workflow
What This Is
These agents make Specflow work with Claude Code as the orchestrator. They ensure your GitHub issues have ARCH, FEAT, and JOURNEY contracts that can be executed:
- At build time — Jest pattern tests catch architectural violations (
npm test -- contracts) - Post-build — Playwright tests verify user journeys work end-to-end
This three-layer approach reduces architectural drift and ensures work meets Definition of Done.
Two execution modes:
- Subagent mode (default) — Claude Code's Task tool spawns one-shot agents that do work and return. Works everywhere.
- Agent Teams mode (Claude Code 4.6+) — Persistent peer-to-peer teammates coordinate via TeammateTool API with three-tier journey gates. Set
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=trueto enable.
ARCH contracts → Build fails if: forbidden patterns in code
FEAT contracts → Build fails if: required patterns missing
JOURNEY contracts → Release blocked if: user flows don't work
How You Use It
You give Claude Code a high-level goal. It figures out which agents to call.
High-level prompt:
"Create tasks to make sure all stories in TODO status are specflow-compliant,
that all contracts are created, and every UI story has a journey contract
with Playwright tests."
Claude Code will:
- Run
board-auditorto check compliance - Run
specflow-uplifteron non-compliant issues - Run
contract-generatorto create YAML contracts - Run
contract-test-generatorto create Jest tests - Run
journey-enforcerto check journey coverage - Run
playwright-from-specflowandjourney-testerto create Playwright tests
You don't need to name agents explicitly. Just describe what you want. The agents are documented so Claude Code knows when to use each one.
But you can be specific if you prefer:
"Run board-auditor on issues #42-#48"
"Run journey-tester for J-AUTH-LOGIN"
Both approaches work. High-level prompts for convenience; specific commands for control.
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.
- 2d ago First seen · 379 lines · 0 tokens per session scan A 6507de0da45c
WORKFLOW is an agent published in the GitHub repository Hulupeep/Specflow (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,154 tokens. 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
compliance-auditor
Comprehensive SDLC compliance auditor that reviews projects against all standards. Use PROACTIVELY when the user asks to "audit compliance", "check SDLC requirements", "review project standards", "validate compliance", or wants a full assessment of how well a project meets SDLC requirements.
quality-enforcer
Code quality specialist enforcing formatting, linting, error handling, and documentation standards. Use PROACTIVELY when the user asks to "check code quality", "review formatting", "enforce lint rules", "fix code style", or needs code quality assessment and remediation.
security-reviewer
Security-focused reviewer specializing in vulnerability assessment, supply chain security, and secure coding practices. Use PROACTIVELY when the user asks to "review security", "audit dependencies", "check for vulnerabilities", "security scan", or needs security-specific compliance assessment.
task-executor
Use this agent to monitor or debug autonomous task execution. Examples - "Why did my task fail?", "Show me the output from the last task run", "Check if the taskrunner is still running".
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions. Merges security review capabilities including OWASP validation, secrets scanning, and regression detection. Uses confidence-based filtering for quality issues and severity classification for…
changelog-updater
Updates CHANGELOG.md following Keep a Changelog conventions based on staged changes.