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 skills add yohey-w/codd-dev --skill codd-generategit clone --depth 1 https://github.com/yohey-w/codd-devWrote 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/yohey-w/codd-dev/codd-generate)<a href="https://agentmods.dev/skills/yohey-w/codd-dev/codd-generate"><img src="https://agentmods.dev/badge/skills/yohey-w/codd-dev/codd-generate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yohey-w/codd-dev/codd-generate"><img src="https://agentmods.dev/badge/skills/yohey-w/codd-dev/codd-generate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01351 |
| Opus 5.5 | $0.00022 | $0.00540 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (115 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,351 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.