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/clawforgeai/clawforge/dbgit clone --depth 1 https://github.com/ClawForgeAI/clawforgeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/clawforgeai/clawforge/db)<a href="https://agentmods.dev/commands/clawforgeai/clawforge/db"><img src="https://agentmods.dev/badge/commands/clawforgeai/clawforge/db.svg" alt="Measured on agentmods" height="20"></a>What 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.00443 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
db 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 today.
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
Database Operations
Run database operations for the ClawForge server package.
Available operations:
- generate: Generate a new migration from schema changes
- migrate: Apply pending migrations (dry-run first)
- seed: Seed the database with default admin user
- studio: Open Drizzle Studio visual browser
- status: Show current migration state
- dry-run: Preview pending migrations without applying
- rollback-plan: Show rollback SQL for the latest migration
Instructions
Ask the user which operation they want to run if not specified in: $ARGUMENTS
For generate:
- Check
server/src/db/schema.tsfor recent changes - Run
pnpm --filter @ClawForgeAI/clawforge-server db:generate - Review the generated SQL in
server/src/db/migrations/ - Report what tables/columns were affected
For migrate:
- First run dry-run to preview:
cd server && npx tsx --env-file=.env src/db/migrate.ts --dry-run - Show the user what will be applied
- Only apply if user confirms:
pnpm --filter @ClawForgeAI/clawforge-server db:migrate
For seed:
- Run
pnpm --filter @ClawForgeAI/clawforge-server db:seed - Confirm seed completed (default credentials: [email protected] / clawforge)
For studio:
- Run
pnpm --filter @ClawForgeAI/clawforge-server db:studio
For status:
- Run
cd server && npx tsx --env-file=.env src/db/migrate.ts --status
For dry-run:
- Run
cd server && npx tsx --env-file=.env src/db/migrate.ts --dry-run
For rollback-plan:
- Run
cd server && npx tsx --env-file=.env src/db/migrate.ts --rollback-plan - Review the generated rollback SQL and any warnings about manual steps
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.
- today First seen · 53 lines · 0 tokens per session scan A 39d9b040b999
db is a command published in the GitHub repository ClawForgeAI/clawforge (17 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 443 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-09-04.
Other commands, from other repositories
spec
Manage specifications in our development process.
ingest-l0
L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
schema
Show SQL schema for a module by reading its migration files.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.