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 iowarp/clio-kit --skill clio-kit-scientific-debugginggit clone --depth 1 https://github.com/iowarp/clio-kitWrote 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/iowarp/clio-kit/clio-kit-scientific-debugging)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-scientific-debugging"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-scientific-debugging/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/iowarp/clio-kit/clio-kit-scientific-debugging"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-scientific-debugging.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.00088 | $0.01771 |
| Opus 5.5 | $0.00035 | $0.00708 |
| Sonnet 5.5 | $0.00018 | $0.00354 |
| Haiku 4.5 | $0.00009 | $0.00177 |
Grade A, and why
clio-kit-scientific-debugging 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Host compatibility
This copy is adapted from Clio Coder. Apply the procedure using the current host's available tools and the user's authorized scope. The tool names, /skill invocations, .clio-coder paths, fleets, approval gates and completion gates below describe Clio Coder; they are not installed or enforced by this skill in another host. Use the host's actual skill invocation and equivalent tools. If no equivalent exists, report the missing capability. Do not assume a tool is unavailable merely because the original headless workflow says so. A referenced agent or skill must be installed before relying on it. Scientific MCPs must be configured separately.
Adapted skills use the clio-kit- prefix to distinguish them from upstream audited skills. For a companion skill named below, select its clio-kit- copy from this collection; native agents, fleets and external programs retain their original names.
Scientific Debugging
Debug by falsification, not by trying fixes. A fix attempted before a confirmed diagnosis is an experiment run without a hypothesis; when it "works" you have learned nothing, and when it does not you have contaminated the evidence.
Anti-trigger: if the failure is a typo, a missing import, or an error message that names its own cause, fix it directly and skip this workflow. The loop below is for failures that survived the first obvious fix.
Arguments
/skill clio-kit-scientific-debugging <failure description>
Everything after the skill name is the failure report: the observed wrong
behavior and whatever has already been tried. There is no operator in a
headless run: ask_user is not registered, so any call is refused as an
unregistered tool rather than answered. If the goal,
a fault-class split, or a ranking call is ambiguous, state your best reading
in Step 1 or Step 3 and proceed; never stall a step waiting for confirmation.
The Loop below is the plan; do not open a task list for it — tasks sits
outside this skill's tool surface and any call to it is refused.
What ships with it
3 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.
- 9d ago First seen · 139 lines · 88 tokens per session scan A a92083613734
clio-kit-scientific-debugging is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 88 tokens to every session and 1,771 once invoked, about $0.0004 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-10-08.
Other skills, from other repositories
experiment-craft
Use this skill when the user wants to debug, diagnose, or systematically iterate on an experiment that already exists, or when they need a structured experiment log for tracking runs, hypotheses, failures, results, and next steps during active research. Apply it to underperforming methods, training that will not…
compile-warning-handler
Compiler warning triage for HPC parallelization. Use when deciding whether to proceed with job execution after compile warnings.
bio-genome-assembly-assembly-polishing
Decides whether and how to polish a draft genome assembly to raise consensus accuracy (QV) with read-type-matched tools - Racon and medaka (ONT consensus), dorado polish, Polypolish and pypolca (Illumina, repeat-aware), Pilon (legacy short-read), NextPolish/NextPolish2, Hapo-G (haplotype-aware), ntEdit, and…
mxl-troubleshoot
This skill should be used when MaxwellLink simulations stall, diverge, or produce missing/incorrect observables; it provides a first-aid checklist for sockets, units, and driver configuration.
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
nonlinear-solvers
Select and configure nonlinear solvers for f(x)=0 or min F(x). Use for Newton methods, quasi-Newton (BFGS, L-BFGS), Broyden, Anderson acceleration, diagnosing convergence issues, choosing line search vs trust region, and analyzing Jacobian quality.