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 commands/rajconnects/founder-stack/schema-gategit clone --depth 1 https://github.com/rajconnects/founder-stackWhat 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.00051 | $0.00850 |
| Opus 5 | $0.00026 | $0.00425 |
| Sonnet 5 | $0.00010 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
schema-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 yesterday.
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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the schema gate.
Arguments: $ARGUMENTS
Steps
-
Resolve files. If
$ARGUMENTSis empty orauto, readmigrationsfrom.claude/project.jsonand pick files in that dir modified within the last hour. Otherwise use the path/glob given. If none found: fail loudly. -
Cache check. For each migration file, compute
sha256sum. If.claude/.schema-gate-cache/<sha>.mdexists, print it, refresh.claude/.schema-gate-passed, and stop. Re-running the gate on unchanged files must not invoke the agent. -
Static pre-pass (deterministic, free). Run
workflow/hooks/schema-static-scan.sh <file>.... If it exits non-zero, print its findings, remove.claude/.schema-gate-passed, and stop — these are unambiguous FAILs the agent cannot rescue. -
Resolve config and parse migration shape. Read
.claude/project.jsononce. Extractstack.supabase_project_refandmigrations. Then parse the migration SQL to extract:new_tables—CREATE TABLE [IF NOT EXISTS] <name>matches.new_columns—ALTER TABLE <t> ADD COLUMN <c>matches.new_indexes—CREATE [UNIQUE] INDEX [CONCURRENTLY] <n> ON <t>matches; record whetherCONCURRENTLYis present. If the migration has none of these (e.g. function-only DDL), skip step 5 and emitverdict: PASS — no schema surface to audit.
-
Launch
schema-analystwith a self-contained prompt containing: the migration file paths,supabase_project_ref, the parsednew_tables/new_columns/new_indexes, and (if--notes <path>was passed) the evolution-notes path. Do NOT ask the agent to re-readproject.json. -
Optional advisors pass. If
--with-advisorswas passed AND the agent returnedverdict: PASS, callmcp__claude_ai_Supabase__get_advisorsonce from this slash command and append a one-line summary. Do not run advisors by default — they are project-wide and noisy. -
Cache and mark. Save the agent output to
.claude/.schema-gate-cache/<sha>.md. On PASS,touch .claude/.schema-gate-passed. On FAIL,rm -f .claude/.schema-gate-passed. -
Print. On PASS, print one line:
schema-gate: PASS — <N> tables, <M> columns, <K> indexes audited. On FAIL or PASS_WITH_WARNINGS, print the agent's terse output verbatim. -
Session hygiene hint (PASS only). Append one line:
If the next task is unrelated to this migration, consider a session reset (in Claude Code: /clear). See docs/session-hygiene.md.Do not print on FAIL — the failure context is what the user needs to diagnose.
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.
- yesterday First seen · 40 lines · 51 tokens per session scan A d7cc01aad6fd
schema-gate is a command published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 850 once invoked, about $0.0003 per session on Opus 5. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.