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/generate-api-clientnpx skills add nerds-odd-e/doughnut --skill generate-api-clientgit 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.00053 | $0.00700 |
| Opus 5 | $0.00026 | $0.00350 |
| Sonnet 5 | $0.00011 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
generate-api-client 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 packages/generated/donut-backend-api in sync with Java
controllers — never hand-edit generated output.
Output: Regenerated client + green frontend tests + summary ending with
## API CLIENT GENERATED.
Never edit generated code directly. This includes whitespace-only cleanup in
sdk.gen.ts, types.gen.ts, and open_api_docs.yaml; if generated output
changes, accept it or fix the generator path.
Git does not use the Nix prefix. All other repo tooling does:
CURSOR_DEV=true nix develop -c …
Do not run raw git diff --check as a generated-client cleanup gate. Use
scripts/check_diff_whitespace.sh, which excludes generated API artifacts from
manual whitespace fixes.
Regenerate when:
- A backend controller signature changed
- A backend data type used by any controller signature changed
pnpm openapi:lintorpnpm format:allfails with OpenAPI validation errors
CURSOR_DEV=true nix develop -c pnpm frontend:test
Fix any broken frontend code that used the old API signatures.
<success_criteria>
- Java controllers fixed at source (not generated files)
pnpm generateTypeScriptrun with Nix prefix- Frontend tests pass after signature changes
- OpenAPI lint passes (fix controllers + regenerate, never hand-edit YAML)
- Final output includes
## API CLIENT GENERATED</success_criteria>
- What triggered regeneration (controller/DTO change, lint failure, etc.).
- Whether frontend call sites needed updates.
- Tests run and confirmed passing.
## API CLIENT GENERATED
<out_of_scope>
- Do not hand-edit
sdk.gen.ts,types.gen.ts, oropen_api_docs.yaml. - Do not use raw
git diff --checkfor generated-client whitespace gates. </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 · 96 lines · 53 tokens per session scan A 2e92fbd65746
generate-api-client is a skill published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 700 once invoked, about $0.0003 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.