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 debabsah/fable-method --skill fable-shipgit clone --depth 1 https://github.com/debabsah/fable-methodWrote 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/debabsah/fable-method/fable-ship)<a href="https://agentmods.dev/skills/debabsah/fable-method/fable-ship"><img src="https://agentmods.dev/badge/skills/debabsah/fable-method/fable-ship/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/debabsah/fable-method/fable-ship"><img src="https://agentmods.dev/badge/skills/debabsah/fable-method/fable-ship.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.00046 | $0.01541 |
| Opus 5.5 | $0.00018 | $0.00616 |
| Sonnet 5.5 | $0.00009 | $0.00308 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade A, and why
fable-ship 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fable-ship
The report is part of the work, not an afterthought. Ship a calibrated claim and the docs that let a stranger redo it.
The report
- Answer first, then the support. Lead with the verdict (done / not done / exact / blocked) in the first line; put evidence underneath, never above.
- Scale the report to the tier. T1 = the verdict, its
Verified:line(s), and the tier line — a few lines, not a document. The full shape here is for T2+. - Separate verified from assumed, out loud — as the method's ledger (canonical shapes: the method skill's ledger section; same tokens every report, and the Stop-hook gate greps for them). Never let an
Assumed:line read like aVerified:one. - Cite specifics: paths, counts,
file:line, the command you ran, the number you saw, before→after deltas. - Report what you observed, not what you intended. If a step was skipped or a test failed, say so with the output.
- Calibrate "done" with a use-boundary. Stamp unproven results PROVISIONAL ("do not quote these yet") and lift it explicitly only when the check passed. Scope the claim to exactly what you measured; put the rest in a visible residual list.
- State the tier and its gates. One line:
Tier: Tn — gates run: <verify / review lenses / human gate>. A skipped gate that leaves no trace is invisible exactly when it matters. - Never soften a real problem — including your own. Flag anything the human must decide (⚠️), state it plainly with the evidence, and repeat the flag into every downstream artifact (PR body, log, memory), not just the chat.
- End with what the reader still owns. Even a perfect report leaves a short list: every
Assumed:line, plus any T3 (outward/production) action gated to the human. Say it explicitly — worry-less means a short, honest residual list, not an empty one. - Close in the reader's language: where we are, what's next. After the ledger, two plain-language lines — the state of the work, and the single next move with whose it is. No session-jargon: a label coined mid-work (a codename, a phase number, an internal shorthand) gets one plain-word gloss or stays out of the report. The reader is catching up, not replaying your process — findings go above; the ending is orientation.
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 · 45 lines · 46 tokens per session scan A 14b85f5dc893
fable-ship is a skill published in the GitHub repository debabsah/fable-method (1 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 1,541 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-31.
Other skills, from other repositories
gh-cli
GitHub CLI (gh) reference for repos, issues, PRs, Actions, releases, gists, projects, codespaces, and the API.
release-management
Cut a semver release from conventional commits — bump, grouped changelog, annotated tag, GitHub release.
finishing-a-development-branch
Guide the completion of a development branch by presenting structured options for merge, PR, or cleanup.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.