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 skills/mtvrkan/senior-dev-kit/db-changenpx skills add mtvrkan/senior-dev-kit --skill db-changegit clone --depth 1 https://github.com/mtvrkan/senior-dev-kitWrote 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/skills/mtvrkan/senior-dev-kit/db-change)<a href="https://agentmods.dev/skills/mtvrkan/senior-dev-kit/db-change"><img src="https://agentmods.dev/badge/skills/mtvrkan/senior-dev-kit/db-change.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.1 | $0.00044 | $0.00379 |
| Opus 5 | $0.00022 | $0.00189 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
db-change 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 5d 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
db-change
Greenfield modeling (no schema exists yet) — produce a data model plan first, no code edits:
ENTITIES: [list] | RELATIONS: [A has-many B, …] | INDEXES: [field → reason]
CONSTRAINTS: [unique, not-null, FK, check] | SQL vs NoSQL: [rationale if a choice is needed]
ANTI-PATTERNS AVOIDED: [what was rejected and why]
Changing an existing schema — produce this analysis before any change:
- AFFECTED: tables / collections / models touched
- DATA LOSS RISK: DROP, rename, type narrowing, NOT NULL on existing rows
- STRATEGY: additive change (nullable column, new table) or multi-step migration
- MIGRATION ORDER: deploy order relative to code changes
- INDEX/CONSTRAINT IMPACT: new indexes, constraint changes, performance effect
- RACE/TRANSACTION RISK: concurrent write safety
- TESTS REQUIRED: what must be verified before applying
Prefer additive changes. Never approve destructive operations without explicit user confirmation.
Deep references: agent_docs/zero-downtime-migration.md — expand/contract phases and deploy ordering; agent_docs/architecture.md — where models and repositories live.
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.
- 5d ago First seen · 32 lines · 44 tokens per session scan A 8f2b3239e31d
db-change is a skill published in the GitHub repository mtvrkan/senior-dev-kit (5 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 379 once invoked, about $0.0002 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 skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…