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 imMamdouhaboammar/get-fable --skill run-skill-generatorgit clone --depth 1 https://github.com/imMamdouhaboammar/get-fableWrote 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/immamdouhaboammar/get-fable/run-skill-generator)<a href="https://agentmods.dev/skills/immamdouhaboammar/get-fable/run-skill-generator"><img src="https://agentmods.dev/badge/skills/immamdouhaboammar/get-fable/run-skill-generator/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/immamdouhaboammar/get-fable/run-skill-generator"><img src="https://agentmods.dev/badge/skills/immamdouhaboammar/get-fable/run-skill-generator.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.00016 | $0.04184 |
| Opus 5 | $0.00008 | $0.02092 |
| Sonnet 5 | $0.00003 | $0.00837 |
| Haiku 4.5 | $0.00002 | $0.00418 |
Grade A, and why
run-skill-generator scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl`. You build (or script) that harness now, commit it alongside This is a copy
95% identical to run-skill-generator — 137 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your job is to produce a skill at <unit>/.claude/skills/run-<unit-name>/
that lets a future agent build, launch, and drive this project from
a clean machine.
The skill has two parts that live together:
<unit>/.claude/skills/run-<unit-name>/
SKILL.md ← agent-facing instructions — SHORT. Points at the driver.
driver.mjs ← (or driver.py, smoke.sh, … — or none: web apps use
chromium-cli off-the-shelf, and the heredoc in
SKILL.md is the script)
That almost always means writing code, not just prose. If the app
has any interactive surface (GUI, TUI, long-running server, REPL), the
future agent needs a programmatic way to poke it. A markdown file by
itself cannot click a button — but sometimes the button-clicker
already exists: for web apps it's chromium-cli, for servers it's
curl. You build (or script) that harness now, commit it alongside
the skill, and the SKILL.md documents how to use it.
Definition of done
You are done when all of these are true:
- You launched the app in this container and interacted with it — not its test suite, the actual running app. For anything with a GUI, that means you have a screenshot file on disk that you took.
- The interaction harness is committed next to the skill. A driver
script, a REPL wrapper, a smoke test, or the
chromium-cliheredoc inline inSKILL.md— whatever you used to drive the app in step 1. (Graduated intoscripts//e2e/? — fine, point at it. Web app withchromium-clioff-the-shelf? — the inline script is the harness; no separate file.) - The
SKILL.mddocuments the harness as the primary agent path — the section a future agent reads first is "run this driver / pipe these commands tochromium-cli," not "runnpm startand a window opens." - Every code block in
SKILL.mdis a command you ran that worked. This session. This container. Not from the README, not inferred.
If you're about to write the skill and you don't have (1), stop. You are about to paraphrase existing docs. That document already exists — it's called the README, and the whole reason you're here is that it wasn't enough.
What ships with it
7 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 · 344 lines · 16 tokens per session scan A 07c490e2240d
run-skill-generator is a skill published in the GitHub repository imMamdouhaboammar/get-fable (4 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 4,184 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 95% identical to run-skill-generator, differing in 137 lines, and is treated as a copy.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
spec-graph
The project's specs are its ground truth: durable documents describing the architecture, decisions, contracts, and boundaries behind the code, organized as a connected graph. Read this skill and reach for the spec tools FIRST — before reading code — whenever you explore the project, plan or start a task, add or change…
brainstorming
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.
reviewing-changes
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.