cc-sdd is a spec-driven development workflow for coding agents: it turns approved software specifications into requirements, designs, task plans, and extended autonomous implementation. Developers use it across several AI coding agents, with independent review and task-level continuation for long-running work. The catalogue entries provide commands, skills, agents, and instructions for using this workflow.
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 gotalab/cc-sdd --skill cc-sdd-new-agentgit clone --depth 1 https://github.com/gotalab/cc-sddWrote 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/gotalab/cc-sdd/cc-sdd-new-agent)<a href="https://agentmods.dev/skills/gotalab/cc-sdd/cc-sdd-new-agent"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/cc-sdd-new-agent/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/gotalab/cc-sdd/cc-sdd-new-agent"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/cc-sdd-new-agent.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.00063 | $0.01051 |
| Opus 5 | $0.00032 | $0.00526 |
| Sonnet 5 | $0.00013 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
cc-sdd-new-agent 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 11d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CC-SDD New Agent Integration
Goal
Add a production-ready agent integration to tools/cc-sdd with complete research, implementation, and verification artifacts.
Use the existing SOP and templates in this repository instead of inventing a new process.
Default Operation Mode
Use plan-first as the default:
- First deliverable:
docs/cc-sdd/plans/agent-plan-{agent-id}.md - Second deliverable (after plan approval): implementation changes in
tools/cc-sdd/...
Do not skip the plan document unless the user explicitly requests direct implementation.
Collect Inputs First
Collect the minimum inputs before editing files:
- Target agent display name and agent id (kebab-case)
- Official documentation URL for command/agent/skills format
- Integration scope:
commands-only,commands+agents, orskills - Whether work type is
new-agentormigration
If any item is unclear, resolve it during Phase 1 research before creating implementation files.
Execution Workflow
1) Run Phase 1 Research
Read docs/cc-sdd/sop-new-agent.md and extract all required spec details from official docs:
- commands directory
- agent directory (if supported)
- documentation filename
- command invocation format
- YAML frontmatter schema for commands and agents (or skills)
- placeholders/arguments format
Record exact values (not assumptions) in the plan document.
2) Create Plan Document
Copy and fill:
docs/cc-sdd/templates/agent-plan-template.md
Include:
- Phase 1 research summary table
- Differences vs nearest existing agent pattern
- 5-step implementation plan
- changed-file list
- verification plan
Write the completed plan to:
docs/cc-sdd/plans/agent-plan-{agent-id}.md
Before implementation, ensure the plan explicitly states:
- integration scope (
commands-only,commands+agents,skills) - whether this is
new-agentormigration - compatibility impact and rollback approach
3) Choose Base Pattern and Implement
Pick the nearest existing implementation and copy from it:
commands-only: start fromtools/cc-sdd/templates/agents/codexor another commands-only agentcommands+agents: start fromtools/cc-sdd/templates/agents/claude-code-agentortools/cc-sdd/templates/agents/opencode-agentskills: start fromtools/cc-sdd/templates/agents/claude-code-skills
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 118 lines · 63 tokens per session scan A 2f79bcd73d70
cc-sdd-new-agent is a skill published in the GitHub repository gotalab/cc-sdd (3,661 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,051 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
todo-for-ai-agent-runtime
Runtime integration skill for external agents connecting to Todo for AI over HTTP API Token / Agent Key, including auth, task lease, events, commit, and task logs.
slice-closure
Decide whether the current slice is ready to close, distinguishing slice completion from full task completion, then persist the result in slice notes and TASKSTATE.md as explicit reviewable closure notes. For single-slice tasks may route directly to delivery. Returns no-op when slice memory would not materially…
task-init
Initialize the official task folder and base task memory inside projects/ /active/YYYY-MM-DD /. Creates README.md, TASKSTATE.md, SOURCEOFTRUTH.md, DECISIONS.md, IMPLEMENTATIONPLAN.md; seeds from PROJECTCHARTER.md when present; emits a multi-repo ## Repositories section in SOURCEOFTRUTH.md when 2+ repos are provided.…
decision-interview
Ask the minimum set of high-value decision questions needed before turning the task into canonical implementation rules. Decisions that would change runtime behavior, data integrity, rollout safety, or test strategy. Use when the missing information is decision-driven (not factual), different answers would change…
godot-scene-plan
Plan the Godot scene and node structure for a 2D or 3D game feature before any GDScript is written: the scene tree, node types and responsibilities, autoloads (singletons), signal wiring, the input map, and the resources and sub-scenes to create. Produces GODOTSCENEPLAN.md, a design-time plan an MCP-driven editor or a…
implementation-plan
Define an incremental, reviewable, production-safe implementation plan for the active task and persist it as IMPLEMENTATIONPLAN.md plus a TASKSTATE.md update. Breaks work into the smallest safe slices with objective, exact scope, ordering rationale, key risks, validation approach, exit criteria, and work complexity…