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-initnpx skills add yohey-w/codd-dev --skill codd-initgit 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.00055 | $0.01045 |
| Opus 5 | $0.00028 | $0.00522 |
| Sonnet 5 | $0.00011 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
codd-init 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoDD Init
Initialize CoDD in the current project, then move immediately into the first scan and validation cycle so the dependency graph starts from a clean baseline.
Usage
Run this skill when a repository does not have a codd/ directory yet and you need to bootstrap CoDD with the official codd CLI entry point.
Instructions
-
Preflight before running
codd init:- Work from the project root where
codd/should be created. - If
codd/already exists, do not re-run init. Inspect the existing CoDD setup instead. - If the
coddcommand is not available, install the package so the console script is onPATHbefore continuing.
- Work from the project root where
-
Collect the required inputs:
- Project name: default to the current directory name unless the user provides a better product name.
- Primary language: choose one of
python,typescript,java, orgo. - Requirements file (optional): if the user already has a requirements document (any format —
.txt,.md,.doc), use--requirementsto import it. CoDD adds frontmatter automatically.
-
Choose the command:
- With existing requirements file (recommended):
codd init --project-name "<project-name>" --language <language> --requirements <path-to-requirements> --dest .
- Without requirements (user will add them later):
codd init --project-name "<project-name>" --language <language> --dest .
-
Run the selected
codd initcommand. -
Confirm the generated skeleton:
codd/codd.yamlcodd/scan/codd/reports/codd/.gitignore.codd_version
-
For an existing project, handle the bootstrap carefully:
- Do not assume old design docs already have CoDD frontmatter. Inspect them before the first scan.
- Prefer adding frontmatter to the documents you want CoDD to track before treating scan results as authoritative.
- Legacy annotation files under
codd/annotations/are optional and backward-compatible. Create them only if the project still uses that workflow.
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 · 111 lines · 55 tokens per session scan A 10d4ad07b93f
codd-init is a skill published in the GitHub repository yohey-w/codd-dev (114 stars, last pushed 21d ago), licensed MIT. It adds 55 tokens to every session and 1,045 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…