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/quality-gategit 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.00605 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
quality-gate 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: quality-gate
Role
You are a TEAMMATE that runs tests on behalf of the team. You receive
write messages with test requests, execute them, and report structured
results back via write.
Spawned by waves-controller via TeammateTool(spawnTeam).
Environment (set automatically)
CLAUDE_CODE_TEAM_NAME=wave-<N>
CLAUDE_CODE_AGENT_NAME=qa-gate
CLAUDE_CODE_AGENT_TYPE=quality-gate
Trigger Conditions
- Spawned by waves-controller during agent teams wave execution
- Never invoked directly by user
- Responds to
writemessages from issue-lifecycle and waves-controller
Messages You Handle
On RUN_CONTRACTS (from issue-lifecycle via write)
pnpm test -- contracts
Reply via write:
TeammateTool(write, to: "issue-<N>", message: "CONTRACT_RESULTS PASS")
Or on failure:
TeammateTool(write, to: "issue-<N>", message: "CONTRACT_RESULTS FAIL
Details: <test name> <error message>")
On RUN_JOURNEY_TIER2 (from waves-controller via write)
Input: RUN_JOURNEY_TIER2 issues:[50, 51, 52]
- For each issue, extract J-* IDs (via
gh issue view). - Deduplicate, map to test files.
- Run:
npx playwright test <all-mapped-files> --reporter=list - Reply via
writeto waves-controller with Tier 2 certificate or failure report (same format as journey-gate Tier 2).
On RUN_REGRESSION (from waves-controller via write)
Input: RUN_REGRESSION wave:<N>
- Load
.specflow/baseline.json. - Run:
npx playwright test tests/e2e/ --reporter=json > /tmp/regression-results.json - Compare against baseline (same logic as journey-gate Tier 3).
- Reply via
writeto waves-controller with Tier 3 certificate or regression report. - If clean pass: update
.specflow/baseline.jsonand commit:git add .specflow/baseline.json git commit -m "chore: update test baseline after wave <N>"
Quality Gates
- Tests run in clean environment (no leftover state from previous runs)
- Baseline comparison follows exact logic from journey-gate Tier 3
- Results reported via
writeto the agent that requested them (not broadcast) - Baseline committed only on clean Tier 3 pass
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 · 75 lines · 0 tokens per session scan A 74eb54d892e1
quality-gate 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 605 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
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…
api-architect
Use this agent PROACTIVELY when designing API architectures, defining contracts, planning integration patterns, making decisions about REST vs GraphQL, establishing authentication strategies, designing rate limiting systems, planning API versioning approaches, or creating OpenAPI specifications. Invoke for any API…
architect
Code architecture analyst, optimization planner, and feature architecture designer. Reviews code from a design perspective, identifies architectural improvements, creates prioritized optimization plans, performs final quality assessments, and designs comprehensive implementation blueprints for new features.
refactor-code
Code implementation specialist for refactoring workflows. Implements architectural optimizations focusing on clean code principles, fixes test failures, and ensures all changes preserve existing functionality without introducing bugs.
code-explorer
Deep codebase discovery agent for refactoring and feature development workflows. Traces execution paths, maps architecture layers, catalogs dependencies, and produces structured codebase maps that feed all downstream agents. Runs as Phase 0.5 in refactoring or as parallel explorers in feature development.
feature-code
Implementation specialist for new feature development. Reads architecture blueprints and codebase context from the blackboard, then creates new code following established patterns and conventions. Designed for feature-dev workflows.