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/yohey-w/codd-dev/codd-generatenpx skills add yohey-w/codd-dev --skill codd-generategit clone --depth 1 https://github.com/yohey-w/codd-devWhat 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.00054 | $0.01351 |
| Opus 5 | $0.00027 | $0.00675 |
| Sonnet 5 | $0.00011 | $0.00270 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
codd-generate 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 3d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoDD Generate
Generate CoDD design documents one wave at a time, validate their frontmatter, refresh the dependency graph, and stop for human approval before advancing to the next wave.
This is for greenfield projects (requirements → design). For brownfield projects (existing code → design), use /codd-restore instead.
Usage
Use this skill after codd init and after requirement documents are ready. Generate only one wave at a time. Never auto-run the next wave without a human decision.
If you have an existing codebase with no requirements, use the brownfield flow instead:
codd extract— reverse-engineer code structurecodd plan --init— generate wave_config from extracted docs/codd-restore— reconstruct design docs from extracted facts
Wave Model
CoDD design generation follows dependency order. Documents in the same wave may be generated together, but later waves must wait until the previous wave is validated and reviewed.
- Wave 1: requirement-only artifacts such as acceptance criteria and decisions
- Wave 2: system-level design derived from requirements plus Wave 1 outputs
- Wave 3: detailed design artifacts derived from approved system design
- Wave 4+: later artifacts only after the previous wave is validated and approved
Auto Wave Config
Since v0.2.0a4, codd generate automatically generates wave_config from requirement documents if it's missing from codd.yaml. You no longer need to run codd plan --init manually before generating. The flow is:
- Write requirements in any format (plain text, markdown, etc.) and import with
codd init --requirements <file>— CoDD adds frontmatter automatically - Run
codd generate --wave 2— wave_config is auto-generated from requirements - Design docs are generated in the correct dependency order
This means the only human input is the requirements. Everything else — wave_config, frontmatter, dependency declarations — is derived automatically.
Prerequisite Checks
Before every generation run, verify these conditions:
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.
- 3d ago First seen · 151 lines · 54 tokens per session scan A 20a8c90bc23f
codd-generate is a skill published in the GitHub repository yohey-w/codd-dev (114 stars, last pushed 22d ago), licensed MIT. It adds 54 tokens to every session and 1,351 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.
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…