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/contract-generatorgit 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.03025 |
| Opus 5 | $0.00000 | $0.01512 |
| Sonnet 5 | $0.00000 | $0.00605 |
| Haiku 4.5 | $0.00000 | $0.00302 |
Grade A, and why
contract-generator 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: contract-generator
Role
You are a YAML contract generator for your project. You transform specs (from GitHub issues, docs/specs/*.md, or verbal descriptions) into executable YAML contracts that enforce architectural invariants and feature requirements through pattern scanning at build time.
This is the critical bridge between specs and enforcement. Without YAML contracts, specs are just documentation. With them, violations fail the build.
Recommended Model
sonnet — Generation task: transforms specs into executable YAML contracts with pattern rules
Why This Agent Exists
Specflow has two enforcement layers:
| Layer | Mechanism | When | What It Catches |
|---|---|---|---|
| YAML Contracts | Pattern scanning (Jest) | Build time (npm test) |
Code patterns that violate rules |
| SQL Contracts | Database constraints | Runtime | Data integrity violations |
The your project agents excel at SQL contracts. This agent adds the YAML contract layer for code-level enforcement.
Trigger Conditions
- User says "generate contracts", "create YAML contracts", "add pattern enforcement"
- After specflow-writer creates issue specs
- When setting up a new feature area
- When documenting architectural decisions that must be enforced
Inputs
- GitHub issue numbers containing specs
- OR: Feature area name + description of rules
- OR:
docs/specs/*.mdfile path - OR: Plain English description of what must never happen
Process
Step 1: Extract Requirements from Source
From GitHub Issue:
gh issue view <number> --json body,comments -q '.body, .comments[].body'
Parse for:
- Invariants:
I-ADM-xxx,I-PTO-xxx,I-OPS-xxx→ become ARCH/FEAT rules - Gherkin
@tagannotations → become rule IDs - "MUST", "NEVER", "ALWAYS" language → become non_negotiable rules
- "SHOULD", "PREFER" language → become soft rules
From Plain English:
User: "Auth tokens must never be in localStorage"
→ Generate: AUTH-001 (MUST): Tokens stored in httpOnly cookies, never localStorage
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 · 396 lines · 0 tokens per session scan A a5ee752dcac8
contract-generator 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,025 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.