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-validatenpx skills add yohey-w/codd-dev --skill codd-validategit 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.00052 | $0.00855 |
| Opus 5 | $0.00026 | $0.00428 |
| Sonnet 5 | $0.00010 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
codd-validate 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoDD Validate
Validate CoDD frontmatter and dependency references before impact analysis so broken metadata does not poison the graph or downstream change-propagation work.
Usage
Run this skill after codd scan --path ., after editing requirement or design documents, or any time you suspect frontmatter or dependency references may be inconsistent.
Instructions
-
Preflight:
- Work from the project root.
- Verify
codd/codd.yamlexists. If not, runcodd initfirst. - If the
coddcommand is not available, install the package so the CLI entry point is onPATHbefore continuing.
-
Run validation:
codd validate --path .
-
Interpret the result:
- PASS: Treat
OK: validated ...output as a pass. Frontmatter is structurally valid enough to proceed, and dependency references are consistent enough for the next step. After a clean pass,codd impactis safe to run. - ERROR: Stop and fix the reported documents before continuing. Use the categories below to decide the repair.
- BLOCKED or WARNING: Read the message, fix what is actionable, and re-run validation until the remaining output is understood.
- PASS: Treat
-
ERROR triage by category:
missing_field: Required frontmatter data is missing or malformed. Open the affected design document and add or repair the needed fields, especiallynode_id,title, anddepends_onwhen the design requires declared upstream dependencies. In current validator output, this often appears as missing or invalid frontmatter rather than a literalmissing_fieldcode.invalid_reference: A document references anode_idthat does not exist or is misspelled. Correct the typo or point the reference at the real upstream node. In current validator output, this usually shows up as undefined-reference messages such as danglingdepends_onordepended_by.circular_dependency: Two or more documents depend on each other in a loop. Revisitdepends_on, remove the back-edge, and restore a one-way dependency order.
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 · 62 lines · 52 tokens per session scan A a8938a66c40e
codd-validate is a skill published in the GitHub repository yohey-w/codd-dev (114 stars, last pushed 22d ago), licensed MIT. It adds 52 tokens to every session and 855 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…