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 commands/zakelfassi/skills-driven-development/skillsgit clone --depth 1 https://github.com/zakelfassi/skills-driven-developmentWhat 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.00009 | $0.00516 |
| Opus 5 | $0.00005 | $0.00258 |
| Sonnet 5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
skills 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 3d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skills
You are being asked to list the skills available in this project's SkDD colony.
What the user typed
/skills $ARGUMENTS
Your task
- Look for the colony registry in this order:
.skills-registry.jsonat the project root (machine-readable).skills-registry.mdat the project root (human-readable)- If neither exists, report: "No SkDD colony detected. Run
skdd init(if you have the CLI) or see docs/integrations/claude-code.md for setup. No skills registered yet."
- Parse the registry. For each active skill, show: name, source, last-used (if present), uses (if present), and description.
- If
$ARGUMENTSis non-empty, treat it as a case-insensitive filter — only show skills whose name or description contains the filter string. - Also list the skills actually present on disk under
.claude/skills/(or whichever plugin/scope provides them). If a skill is on disk but not in the registry, flag it as "unregistered — consider adding to.skills-registry.md". If a skill is in the registry but not on disk, flag it as "dangling — file missing". - Format the output as a table with columns: Skill, Source, Status, Description. Use Markdown so it renders cleanly in Claude Code's chat.
What to do next
After listing, suggest one follow-up based on what you see:
- If the registry is empty: suggest
/forge <name>to create the first skill. - If there are unregistered skills on disk: suggest updating
.skills-registry.md(offer to do it inline). - If there are dangling entries: suggest running
skdd validateto clean them up, or ask whether to remove them. - If everything is tidy: suggest the user look for repeated work in the current session that could become a new skill.
Rules
- Never invent skills that aren't in the registry or on disk.
- Never modify the registry without asking first — listing is read-only by default.
- If
skddCLI is available on the user's PATH, mention that they can also runskdd listfrom a terminal for a harness-agnostic view.
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.
- 3d ago First seen · 41 lines · 9 tokens per session scan A 615054cefe5f
skills is a command published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 516 once invoked, about $0.0000 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 commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
rust-features
Get Rust version changelog and new features.
diff
Compare two SKILL.md files section-by-section. Parses frontmatter and body sections independently, showing exactly what changed.
writing:review
Exhaustive parallel editorial review of written content.
add-skill
Scaffold a new skill with validation, plugin generation, and README update.
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.