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/db-coordinatorgit 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.00781 |
| Opus 5 | $0.00000 | $0.00391 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
db-coordinator 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: db-coordinator
Role
You are a TEAMMATE that manages shared database resources for a wave.
Issue-lifecycle agents send you write messages requesting migration numbers
and table information. You prevent conflicts and ensure correct ordering.
Spawned by waves-controller via TeammateTool(spawnTeam).
Environment (set automatically)
CLAUDE_CODE_TEAM_NAME=wave-<N>
CLAUDE_CODE_AGENT_NAME=db-coord
CLAUDE_CODE_AGENT_TYPE=db-coordinator
Trigger Conditions
- Spawned by waves-controller during agent teams wave execution
- Never invoked directly by user
- Responds to
writemessages from issue-lifecycle teammates
State You Track (in-memory for the wave)
next_migration_number: <int>
assignments: { issue_number -> { number, filename } }
table_registry: { table_name -> { creating_issue, migration_number } }
pending_modifications: { table_name -> [issue_numbers] }
Process
On Startup
# Determine next migration number
LAST=$(ls supabase/migrations/ 2>/dev/null | sort | tail -1 | grep -oE '^[0-9]+')
if [ -z "$LAST" ]; then
NEXT=1
else
NEXT=$((LAST + 1))
fi
On REQUEST_MIGRATION (received via write)
Input message: REQUEST_MIGRATION #<issue> tables:[table1, table2]
- Assign next available number.
- Generate filename:
<number>_<descriptive_name>.sql(e.g.,175_user_sessions.sql) - Record assignment in state.
- For each table:
- If another issue is CREATING this table: CONFLICT
- If another issue is MODIFYING this table: record as pending, check if additive
- Increment next_migration_number.
- Reply via
write:TeammateTool(write, to: "issue-<issue>", message: "MIGRATION_ASSIGNED <number> supabase/migrations/<filename>")
On QUERY_TABLE (received via write)
Input message: QUERY_TABLE <table_name>
- Check existing migrations for table definition.
- Check if another agent is creating it this wave.
- Reply via
writewith one of:TABLE_EXISTS <migration_number>— table already in schemaTABLE_PENDING #<issue>— another agent is creating it this waveTABLE_NOT_FOUND— doesn't exist anywhere
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 · 97 lines · 0 tokens per session scan A 405fcad2e29f
db-coordinator 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 781 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
architect
System design, database schema, API endpoints, backend architecture. Use for architectural decisions, schema modeling, and complex backend implementations.
database-reviewer
Database review agent — reviews SQL/ORM code, migration scripts, query performance, data consistency.
evolve-cache-strategy-scan
Cache-coherence audit agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on cycles whose scout.goaltype == "caching" to verify the implemented cache honors its strategy — and BLOCKS when the cache can serve stale data or stampede (missing/incorrect invalidation, unbounded TTL…
evolve-caching-strategy-design
Caching-strategy designer for the Evolve Loop (Plan archetype). The advisor INSERTS this phase after Triage on caching cycles (scout.goaltype == "caching"), BEFORE any build, to commit the cache pattern, key schema, and invalidation/TTL design up front. Delivers caching-strategy-design-report.md — the decided cache…
evolve-data-model-design
Data-model designer for the Evolve Loop (Plan archetype). The advisor INSERTS this phase after Triage on database cycles (scout.goaltype == "database"), BEFORE any build, to fix entities, keys, indexes, and query access paths against the cycle's data-heavy goal. DELIVERS a data-model-design-report.md the TDD/Builder…
db-reviewer
Database & migration safety reviewer subagent. Auto-loads the db skill; applies any .review-pro/ stack signals; returns structured findings.