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 benjaminard/fable-skills --skill verified-donegit clone --depth 1 https://github.com/benjaminard/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/benjaminard/fable-skills/verified-done)<a href="https://agentmods.dev/skills/benjaminard/fable-skills/verified-done"><img src="https://agentmods.dev/badge/skills/benjaminard/fable-skills/verified-done.svg" alt="Measured on agentmods" 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.00068 | $0.00631 |
| Opus 5 | $0.00034 | $0.00316 |
| Sonnet 5 | $0.00014 | $0.00126 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
verified-done 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 8d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verified Done
"Done" is a claim about evidence, not about effort. Before you report progress or completion, every claim you make must be backed by a tool result from this session that you can point to.
The audit rule
Before reporting progress, audit each claim against a tool result from this session:
- "The tests pass" requires a test run in this session, after your last edit, with passing output you saw. A test run from before your most recent change proves nothing.
- "The build succeeds" requires a build you ran, after the final edit.
- "The bug is fixed" requires reproducing the failure, applying the fix, and observing the failure gone. If you never reproduced it, say "I made a change that should address it, but I could not reproduce the original failure to confirm."
- "The feature works" requires exercising the feature: running the code path, hitting the endpoint, loading the page. Reading your own diff is not exercising the feature.
If a claim has no tool result behind it, do not soften it into "should." Label it: "unverified." Then either verify it now or tell the user plainly that it is unverified and why.
Report outcomes faithfully
- If tests fail, say so and include the failing output. Do not summarize a failure as "mostly passing."
- If you skipped a step, say that you skipped it and why.
- If something is done and verified, state it plainly without hedging. Hedging on verified work is as misleading as confidence on unverified work.
- Never end a status report with optimism the evidence does not support. "3 of 5 subtasks verified, 2 remaining" beats "great progress, nearly there."
The completion checklist
Run this before your final message on any coding task:
- Did I run the code, tests, or build after my last edit?
- Can I point to the specific tool output that proves each claim in my summary?
- Did I re-read the original request and confirm I did what was asked, all of it, and only it?
- Is every unverified item explicitly labeled as unverified in my summary?
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.
- 8d ago First seen · 42 lines · 68 tokens per session scan A 0838c71fee72
verified-done is a skill published in the GitHub repository benjaminard/fable-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 631 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
guidance
Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework.
alterlab-paper-writer
Drafts and revises academic papers through a 12-agent pipeline with hardened LaTeX output (apa7 document class, justified text, table column-width formula, centered bilingual abstracts, standardized font stack, PDF compiled from LaTeX), supporting IMRaD, literature review, theoretical, case study, policy brief, and…
alterlab-pyhealth
Develops, tests, and deploys clinical machine learning models with the PyHealth healthcare AI toolkit. Use when working with electronic health records (EHR), clinical prediction tasks (mortality, readmission, drug recommendation), medical coding systems (ICD, NDC, ATC), physiological signals (EEG, ECG), healthcare…
alterlab-imaging-data-commons
Query and download public cancer imaging data from the NCI Imaging Data Commons (IDC) using the idc-index Python package, filtering by metadata, visualizing in-browser, and checking licenses, with no authentication required. Use when obtaining large-scale radiology (CT, MR, PET) or digital pathology DICOM datasets for…
alterlab-phylogenetics
Build phylogenetic trees end-to-end from raw sequences — MAFFT multiple sequence alignment, optional TrimAl trimming, IQ-TREE 2 maximum-likelihood inference with model selection and bootstraps, FastTree for large datasets, then visualize with ETE3 or FigTree. Use when reconstructing trees from sequences (FASTA) for…
alterlab-molecular-dynamics
Runs and analyzes molecular dynamics simulations with OpenMM and MDAnalysis — setting up protein and small-molecule systems, assigning force fields, running energy minimization and production MD, and analyzing trajectories (RMSD, RMSF, contact maps, free energy surfaces). Use when simulating protein or ligand…