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/zakelfassi/skills-driven-development/skillforgenpx skills add zakelfassi/skills-driven-development --skill skillforgegit 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.00041 | $0.00822 |
| Opus 5 | $0.00020 | $0.00411 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
skillforge 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SkillForge
Create well-formed, spec-compliant skills from observed patterns.
When to Forge
✅ Forge when:
- You've done the same sequence 2-3 times in a session
- A project convention isn't documented anywhere
- You solved a hard problem with a reusable solution
- Someone asks you to create a skill
❌ Don't forge when:
- It's a one-time task
- An existing skill already covers it (update instead)
- The "skill" is just a single command (use a script alias)
Steps
1. Name the pattern
- What problem does this skill solve?
- What triggers it? (be specific — the
descriptionfield is the discovery surface) - What are the inputs and outputs?
2. Choose a name
kebab-case, 1-64 characters- Verb-led when possible:
deploy-preview,scaffold-component,triage-bug - One responsibility per skill
3. Create the skill directory
mkdir -p .claude/skills/<skill-name>
(Or .codex/skills/, .cursor/skills/, .github/skills/, etc. — match the harness. In Claude Code this plugin targets .claude/skills/.)
4. Write SKILL.md
Use this skeleton:
---
name: <skill-name>
description: <what it does>. Use when <triggers>.
metadata:
forged-by: <agent-id>
forged-from: <session-or-context>
forged-reason: "<why this was created>"
status: active
---
# <Skill Name>
## Inputs
- ...
## Steps
1. ...
2. ...
## Conventions
- Project-specific patterns that apply
## Edge Cases
- Known gotchas or special handling
5. Add scripts (optional)
If the skill involves file generation or automation:
.claude/skills/<skill-name>/
├── SKILL.md
├── scripts/
│ └── run.sh # Executable automation
└── references/
└── conventions.md # Detailed reference (keeps SKILL.md lean)
6. Register the skill
Update .skills-registry.md at the project root (same level as .claude/). Create it if it doesn't exist:
| <skill-name> | local | <today> | 1 | <description> |
If the project uses the machine-readable registry (.skills-registry.json), update it too — the skdd CLI handles both formats automatically.
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 · 121 lines · 41 tokens per session scan A 5c06ae560c66
skillforge is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 822 once invoked, about $0.0002 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
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
comet-classic
Comet Classic 工作流（OpenSpec + Superpowers）。当用户明确调用 /comet-classic、要求启动或恢复 Comet Classic，或 resume-probe 返回可无歧义恢复的 active Classic change 时使用。.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or iterate on skill quality. Triggers: "create a skill", "make a…
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.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.