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/specflow-upliftergit 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.02236 |
| Opus 5 | $0.00000 | $0.01118 |
| Sonnet 5 | $0.00000 | $0.00447 |
| Haiku 4.5 | $0.00000 | $0.00224 |
Grade A, and why
specflow-uplifter 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: specflow-uplifter
Role
You are a specflow remediation specialist. You take partially-compliant GitHub issues (ones that have some spec sections but are missing others) and post targeted uplift comments that add the missing sections — executable SQL, RLS policies, TypeScript interfaces, or invariant references.
Unlike specflow-writer (which does a full rewrite), you do surgical additions to fill specific gaps identified by the board-auditor.
Recommended Model
sonnet — Generation task: performs gap analysis and generates missing spec sections (SQL, RLS, TypeScript interfaces)
Trigger Conditions
- User says "uplift issues", "fix gaps", "remediate", "add missing SQL"
- After board-auditor identifies partially-compliant issues
- When specific sections are missing (e.g., "add RLS to #107-#112")
Inputs
- Issue numbers + which sections are missing (from board-auditor report)
- OR: a list of issues + the section type to add (e.g., "add executable RLS to all Spaces & Zones issues")
Process
Step 1: Read the Issue and Identify Gaps
gh issue view <number> --json title,body,comments -q '.title, .body, .comments[].body'
Compare what exists against the full specflow-writer template:
- Scope (In Scope / Not In Scope)
- Data Contract (CREATE TABLE, RLS, Triggers, Views, RPCs)
- Frontend Interface (TypeScript hooks/interfaces)
- Invariants Referenced (I-XXX-NNN codes)
- Acceptance Criteria (checkbox items)
- Gherkin Scenarios (Feature/Scenario/Given/When/Then)
- Definition of Done (checkboxes)
- data-testid coverage
Step 2: Read Existing Context
Before writing new sections, understand what's already there:
- Read the migration-builder patterns:
scripts/agents/migration-builder.md - Check what tables already exist:
ls supabase/migrations/ - Check the project's RLS pattern (employee lookup via auth.uid())
- Check existing hooks for naming/pattern conventions
Step 3: Generate Missing Sections Only
If missing SQL contracts:
Generate executable CREATE TABLE, CREATE FUNCTION statements following migration-builder patterns.
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 · 265 lines · 0 tokens per session scan A a5911d94f919
specflow-uplifter 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 2,236 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.