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/nerds-odd-e/doughnut/database-erdnpx skills add nerds-odd-e/doughnut --skill database-erdgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWhat 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.00071 | $0.00825 |
| Opus 5 | $0.00036 | $0.00413 |
| Sonnet 5 | $0.00014 | $0.00165 |
| Haiku 4.5 | $0.00007 | $0.00082 |
Grade A, and why
database-erd 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
Purpose: Keep the schema diagram accurate after Flyway migrations — never hand-edit the Mermaid block.
Output: Updated docs/database-erd.md + summary ending with
## ERD EXPORTED.
Run when:
- A new or changed Flyway migration alters tables, columns, or constraints
- The ERD needs to match the current migrated schema
Git does not use the Nix prefix. All other repo tooling does:
CURSOR_DEV=true nix develop -c …
Implementation:
- Script:
scripts/export_database_erd.py - Output:
docs/database-erd.md - Omits
flyway_schema_historyfrom the diagram
Overrides (optional):
| Variable | Default |
|---|---|
DONUT_ERD_SCHEMA |
(auto: development → test → e2e) |
DONUT_ERD_MYSQL_HOST |
127.0.0.1 |
DONUT_ERD_MYSQL_PORT |
3309 |
DONUT_ERD_MYSQL_USER |
doughnut |
DONUT_ERD_MYSQL_PASSWORD |
doughnut |
CURSOR_DEV=true nix develop -c python3 scripts/export_database_erd.py
Or:
CURSOR_DEV=true nix develop -c pnpm export:database-erd
<success_criteria>
- MySQL reachable on 127.0.0.1:3309 with user
doughnut - At least one migrated schema available (or
DONUT_ERD_SCHEMAset) - Exporter run with Nix prefix
docs/database-erd.mdupdated and ready to commit- Final output includes
## ERD EXPORTED</success_criteria>
- Schema catalog used (auto-selected or
DONUT_ERD_SCHEMAoverride). - Whether
docs/database-erd.mdchanged.
## ERD EXPORTED
<out_of_scope>
- Do not hand-edit the Mermaid block in
docs/database-erd.md. </out_of_scope>
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 · 107 lines · 71 tokens per session scan A 1a4d0a10aee3
database-erd is a skill published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 825 once invoked, about $0.0004 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 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…