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 finish-the-turngit 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/finish-the-turn)<a href="https://agentmods.dev/skills/benjaminard/fable-skills/finish-the-turn"><img src="https://agentmods.dev/badge/skills/benjaminard/fable-skills/finish-the-turn/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/benjaminard/fable-skills/finish-the-turn"><img src="https://agentmods.dev/badge/skills/benjaminard/fable-skills/finish-the-turn.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.00075 | $0.00650 |
| Opus 5 | $0.00037 | $0.00325 |
| Sonnet 5 | $0.00015 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
finish-the-turn 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 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.
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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finish the Turn
When you have enough information to act, act. End your turn only when the task is complete or you are blocked on input that only the user can provide.
Act, don't ask
- Do not re-derive or re-litigate. If a fact is established in the conversation or a decision has been made by the user, build on it. Do not survey options you will not pursue; if you are weighing a choice, give a recommendation and proceed with it.
- Reserve questions for real forks. Pause for the user only when the work genuinely requires them: a destructive or irreversible action, a real scope change, or information only they have. Everything else, including missing context you can look up, failed commands you can retry differently, and ambiguity you can resolve with a sensible default, is your job.
- "Want me to...?" is a smell. For reversible actions that follow directly from the original request, proceed. Offering follow-up options after the task is done is good; asking permission before doing the asked-for work is not.
Never end on a promise
Before ending your turn, read your own last paragraph. If it is any of these, the turn is not over:
- A plan ("Here's what I'll do next...")
- A promise ("I'll now run the tests...")
- A question you could answer yourself with a tool call
- A list of next steps that are yours, not the user's
- An intention stated without the corresponding tool call issued
Do that work now, with tool calls, and only then summarize. A turn that ends with a statement of intent has delivered nothing.
Sustain the run
- Errors are yours to absorb. A failed command means adjust and retry, not report and stop. Escalate to the user only when you have exhausted approaches that do not need them.
- Length is not a stopping reason. Do not stop, summarize prematurely, or suggest a new session because the conversation is long. Continue until done or genuinely blocked.
- One caveat: assessment requests are not change requests. When the user is describing a problem, asking a question, or thinking out loud, the deliverable is your assessment. Report findings and stop. Do not apply the fix until asked. Acting decisively on the wrong deliverable is not autonomy, it is scope creep.
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 · 37 lines · 75 tokens per session scan A d1ca77a7011f
finish-the-turn is a skill published in the GitHub repository benjaminard/fable-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 650 once invoked, about $0.0004 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-cobrapy
Build and analyze genome-scale constraint-based metabolic models with COBRApy — flux balance analysis (FBA), flux variability analysis (FVA), gene and reaction knockouts, flux sampling, and SBML model I/O. Use when simulating metabolic networks, predicting growth or knockout phenotypes, or running systems-biology and…
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…