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 zakelfassi/skills-driven-development --skill skillforgegit clone --depth 1 https://github.com/zakelfassi/skills-driven-developmentWrote 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/zakelfassi/skills-driven-development/skillforge)<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/skillforge"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/skillforge/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/zakelfassi/skills-driven-development/skillforge"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/skillforge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00041 | $0.00822 |
| Opus 5.5 | $0.00016 | $0.00329 |
| Sonnet 5.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 1mo 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.
- 1mo 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 3mo ago), licensed MIT. It adds 41 tokens to every session and 822 once invoked, about $0.0002 per session on Opus 5.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
code-simplifier
Always-active simplicity rules: no speculative abstractions, one job per function, max 30 lines, flat over nested with early returns, descriptive names, comments explain why.
critical-review
4-phase adversarial review protocol: pre-flight analysis, adversarial execution check, self-correction loop, and [VALIDATION] report.
agent-delegation
Rules for when and how to spawn sub-agents: Explore for 3+ file reads, parallel agents for independent tasks, summaries only — raw output never enters main context.
memory-first
Lookup chain enforced before any file read or search: project and global memory, grep/glob, targeted read — stop at the first step that answers.
verbosity
Response verbosity protocol: reads the level from /.claude/memory/verbosity.md and applies the MIN, INFO or VERBOSE output rules to every reply.
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…