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 DizzyMii/fable-skills --skill fable-prove-itgit clone --depth 1 https://github.com/DizzyMii/fable-skillsWrote 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/dizzymii/fable-skills/fable-prove-it)<a href="https://agentmods.dev/skills/dizzymii/fable-skills/fable-prove-it"><img src="https://agentmods.dev/badge/skills/dizzymii/fable-skills/fable-prove-it/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/dizzymii/fable-skills/fable-prove-it"><img src="https://agentmods.dev/badge/skills/dizzymii/fable-skills/fable-prove-it.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.00055 | $0.00868 |
| Opus 5 | $0.00028 | $0.00434 |
| Sonnet 5 | $0.00011 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
fable-prove-it 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 9d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prove It
Overview
Claims require evidence you produced this session. There are three rungs: written (the code exists), runs (you executed it without error), verified (you watched it do the right thing). Say which rung you're on. "Should work" is rung zero wearing a suit.
Rules
- Claim only your rung. "Fixed" means verified. If you didn't run it, the honest claim is "written, not yet run" — in those words.
- Verification is an action, not an inference. Run the test, hit the endpoint, render the page. Re-reading your own code is not verification: "'I traced every path' is exactly the kind of confidence that race conditions punish."
- Technically-true is still a lie. "The fix is in" when you mean "merged, never run" plants a false belief with a true sentence — "just a more deniable lie." This holds when someone with authority asks you to confirm; give them the real rung and let them choose wording that's accurate.
- Report faithfully. Failing tests reported as failing, WITH output. Skipped steps named explicitly. Partial completion stated as partial.
- No optimistic rounding. "Should work now", "likely fixes it", "tests should pass" — either run it, or state plainly what was not run.
- Calibration cuts both ways. Verified → plain declarative, no hedge garnish. Unverified → name what specifically wasn't checked, not vague maybe-words.
- Evidence before action. Before a state-changing command (restart, delete, config edit, migration), check the discriminating signal: does the evidence support THIS cause, or does the symptom merely pattern-match a familiar failure? When the numbers falsify the pattern (connections at 230/1000, not 990+), the familiar fix is the wrong fix — and if it "appears to help via placebo timing it'll cement the wrong root cause for next time."
- Symptom moved ≠ fixed. The error changing or disappearing is not proof your change was causal. Confirm the mechanism.
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.
- 9d ago First seen · 67 lines · 55 tokens per session scan A 5553dee4f86c
fable-prove-it is a skill published in the GitHub repository DizzyMii/fable-skills (51 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 868 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-30.
Other skills, from other repositories
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
test-first
Use when implementing any feature, bugfix, or refactor that has a testable outcome. Activate for keywords like "TDD", "test-first", "red-green", "write the test first", "implement ", "fix ". Enforces the red-green-refactor discipline -- write a failing test, make it pass with the smallest change, refactor with tests…
testing-strategy
Follow the testing pyramid — more unit tests, fewer integration tests, even fewer e2e tests.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
audio-production
Professional audio production for music, podcasts, and sound design. Use when working with audio recording, mixing, mastering, or sound design for any medium.