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/theam/facility/new-migrationgit clone --depth 1 https://github.com/theam/facilityWhat 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.00014 | $0.00276 |
| Opus 5 | $0.00007 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
new-migration 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 2d 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.
What it actually says
Create a new database migration following STANDARD.md's Database section.
- Locate the migrations directory (
migrations/,supabase/migrations/,db/migrations/,prisma/migrations/— whichever this repo uses) and follow its existing naming convention (timestamp prefix, snake_case description). - Create a NEW file. Never modify or delete an existing migration — they are
append-only; the
migrations-immutableguard and the file hooks enforce it. - Safety defaults in the scaffold, adapted to this repo's stack:
- New tables start closed: enable row/document-level access control where supported, deny by default, grant only the minimum operations.
- Authorization routes through the repo's shared helper layer — no inline token/claim parsing in policies.
- Destructive operations (drop, irreversible data rewrites) get a written justification comment and, where the stack supports it, a down path.
- If the feature needs realistic data to test, update the seeds in the same change.
- Verify: run the repo's migration apply/reset command if one exists, then
node guards/run.mjs --only=migrations-immutable.
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.
- 2d ago First seen · 25 lines · 14 tokens per session scan A 80edd90a7396
new-migration is a command published in the GitHub repository theam/facility (43 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 276 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.