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 skilletmd/skillet --skill skillet-creategit clone --depth 1 https://github.com/skilletmd/skilletWrote 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/skilletmd/skillet/skillet-create)<a href="https://agentmods.dev/skills/skilletmd/skillet/skillet-create"><img src="https://agentmods.dev/badge/skills/skilletmd/skillet/skillet-create/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/skilletmd/skillet/skillet-create"><img src="https://agentmods.dev/badge/skills/skilletmd/skillet/skillet-create.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.00063 | $0.02268 |
| Opus 5 | $0.00032 | $0.01134 |
| Sonnet 5 | $0.00013 | $0.00454 |
| Haiku 4.5 | $0.00006 | $0.00227 |
Grade A, and why
skillet-create 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 12d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skillet create (/skillet create)
Most people cannot answer "what skill do you want to write?" They can answer "yes, that one" when you show them something they already do. So this playbook never opens with a blank page. It reads the work that already happened, proposes candidates with evidence, and carries the one they pick all the way to a live skill page.
Six phases, in order. Do not skip, do not merge, do not run more than one skill per invocation.
0. Say what you are about to read
One line, before you read anything. Not a privacy essay, a scope statement:
Reading this session, this project's recent transcripts, and its conventions files to find what you keep doing. Stays on your machine.
Then read. Everything in phase 1 is local. Nothing is sent anywhere until the user approves an upload in phase 4.
Never widen the scope on your own. Other projects, other repos, and shell history are out unless the user names them. If the current project yields nothing, ask before reaching further.
1. Mine the evidence
Work the ladder top-down. Stop when you have enough for three honest candidates.
- This session. Already in your context and free. What did the user correct you on? What did they explain that they clearly explain often?
- This project's transcripts. Claude Code keeps them at
~/.claude/projects/<slugified-cwd>/*.jsonl; Codex at~/.codex/sessions/. Grep for repeated instruction shapes rather than reading whole files: "always", "never", "remember to", "don't forget", "like last time", "same as", "I told you". Repetition is the signal. A thing said once is a preference; a thing said four times is a skill. - Conventions the user already wrote down.
CLAUDE.md,AGENTS.md,.cursorrules,CONTRIBUTING.md. These are proto-skills that never got packaged. A section that keeps getting cited is the strongest candidate in the repo. - Their own commits.
git log --author="$(git config user.email)" --oneline -50plus the shape of their diffs. What ritual do they run before every push?
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.
- 12d ago First seen · 233 lines · 63 tokens per session scan A f2d5ba9ea4c5
skillet-create is a skill published in the GitHub repository skilletmd/skillet (3 stars, last pushed 13d ago), licensed Apache-2.0. It adds 63 tokens to every session and 2,268 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-31.
Other skills, from other repositories
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.