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-evolvenpx skills add yohey-w/codd-dev --skill codd-evolvegit 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.00086 | $0.05106 |
| Opus 5 | $0.00043 | $0.02553 |
| Sonnet 5 | $0.00017 | $0.01021 |
| Haiku 4.5 | $0.00009 | $0.00511 |
Grade A, and why
codd-evolve 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoDD Evolve — Conversational Brownfield Evolution
Take a Lord-style natural-language change request and automatically determine which design docs, lexicon entries, source files, and tests must move together to preserve CoDD coherence. The user expresses intent; this skill figures out scope.
When to Use
- The user describes a functional change to an existing system, not a bug
- Examples of trigger phrases:
- "Add a logout button to the admin nav"
- "Change course management — courses should be a shared master with separate delivery targets"
- "Restructure the learner list to drill down: facility → learner → course → progress"
- "Remove the daily log append step from the karo completion flow"
- "受講者管理を施設フィルター起点に変更"
- The user does NOT want to think about which design docs, lexicon entries, or source files to touch
- The project is already CoDD-initialized (has
codd/codd.yamland at least the design doc layout)
Do NOT use this for:
- Greenfield generation from scratch — use
/codd-initthen/codd-generate - Pure bug fix where requirements and design are correct — use
codd fixorcodd fix [PHENOMENON] - Reverse-engineering an undocumented codebase — use
codd extract(or/codd-restore) - Single-doc impact analysis only — use
/codd-impact - Code-only refactoring with no behavioral change — use
codd propagate
What This Does — Role Separation
This skill makes a single contract explicit:
| Layer | Who decides | What |
|---|---|---|
| Intent | User | "I want X" in natural language |
| Strategic constraints | User | North star, hard prohibitions, breaking-change tolerance |
| Impact scoping | This skill | Which design docs, lexicon, source files, tests are affected |
| Doc updates | This skill + CoDD | Update requirements + every affected design doc in coherent order |
| Lexicon updates | This skill | Detect new terms, ask user before adding, then update lexicon |
| Implementation | CoDD CLI | codd implement from updated design |
| Verification | CoDD CLI | codd verify — must reach red 0 |
| Coherence finalization | CoDD CLI | codd propagate for cross-doc consistency |
| Failure judgment | You (orchestrator) | Decide retry vs ask user vs abort |
| Final approval | User | Review the PR / diff post-hoc |
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 · 339 lines · 86 tokens per session scan A 28a823acaaed
codd-evolve is a skill published in the GitHub repository yohey-w/codd-dev (114 stars, last pushed 21d ago), licensed MIT. It adds 86 tokens to every session and 5,106 once invoked, about $0.0004 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
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
creating-skills
Guide for creating Claude Code skills following Anthropic's official best practices. Use when user wants to create a new skill, build a skill, write SKILL.md, update an existing skill, or needs skill creation guidelines. Provides structure, frontmatter fields, naming conventions, and new features like dynamic context…