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/arroyo-gonzalo/codex-devkit/database-changenpx skills add Arroyo-Gonzalo/codex-devkit --skill database-changegit clone --depth 1 https://github.com/Arroyo-Gonzalo/codex-devkitWhat 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.00043 | $0.00692 |
| Opus 5 | $0.00022 | $0.00346 |
| Sonnet 5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
database-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 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.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Change
Purpose
Design and implement database changes safely while preserving data integrity, compatibility, and maintainability.
Prefer incremental, reversible, and well-documented changes over destructive operations.
Workflow
1. Understand the change
Identify:
- business objective;
- affected entities;
- affected tables;
- affected relations;
- expected data flow;
- backward compatibility requirements;
- deployment constraints.
Do not modify the schema before understanding existing data.
2. Inspect the current model
Inspect:
- schema;
- ORM models;
- existing migrations;
- indexes;
- constraints;
- foreign keys;
- relationships;
- queries using the affected objects.
Understand how existing code depends on the current schema.
3. Design the database change
Determine:
- new tables;
- modified tables;
- new columns;
- removed columns;
- renamed columns;
- indexes;
- unique constraints;
- foreign keys;
- nullability;
- defaults;
- transactions.
Prefer extending existing structures over replacing them.
4. Review compatibility
Evaluate:
- existing production data;
- migration safety;
- rollback feasibility;
- deployment order;
- coexistence of old and new application versions;
- temporary compatibility requirements.
Avoid breaking existing deployments.
5. Review query impact
Check:
- query performance;
- indexes;
- joins;
- filtering;
- pagination;
- sorting;
- aggregation;
- locking;
- transaction boundaries.
Avoid introducing unnecessary full-table scans.
6. Review integrity
Verify:
- referential integrity;
- uniqueness;
- cascading behavior;
- orphan records;
- transaction consistency;
- concurrency;
- optimistic or pessimistic locking when appropriate.
Protect business invariants.
7. Implement
Prefer:
- migrations;
- parameterized queries;
- repository reuse;
- explicit transactions;
- existing ORM conventions.
Avoid:
- schema synchronization in production;
- destructive operations without justification;
- duplicated persistence logic.
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 · 204 lines · 43 tokens per session scan A 16b0effdeedf
database-change is a skill published in the GitHub repository Arroyo-Gonzalo/codex-devkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 692 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…