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-workflow-distillergit 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-workflow-distiller)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-workflow-distiller"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-workflow-distiller/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-workflow-distiller"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-workflow-distiller.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.00087 | $0.02589 |
| Opus 5.5 | $0.00035 | $0.01036 |
| Sonnet 5.5 | $0.00017 | $0.00518 |
| Haiku 4.5 | $0.00009 | $0.00259 |
Grade A, and why
clio-kit-workflow-distiller scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Reconstruct: `bash curl ...` (ran), `write normalize.py` + `bash python3 How it starts
The opening of the file, as written. The whole thing — 202 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.
Workflow Distiller
Turn a workflow that actually ran into a reusable skill. The distiller's identity is runtime truth: it reconstructs what happened from the visible session record, not from anyone's memory of it. Skip the ceremony when there is no prior workflow; a from-scratch skill is a SKILL.md written directly, following skill-craft. skill-craft also governs how every skill this distiller produces is written: description, body, and pruning rules live there, not here.
Arguments
/skill clio-kit-workflow-distiller [<what to distill>]
With arguments, the text names the workflow to distill; without, distill whichever workflow just ran in this session. Everything else in the request (the conversation so far) is the session record Phase 1 reconstructs from, not more arguments.
A live operator can answer Phase 2's interview and Phase 4's design gate for
real - treat a real, answered ask_user reply as proof an operator is
present and continue asking one question per round. 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. When that
is the run's condition, do not wait for a reply that cannot come: answer
every remaining interview question and the Phase 4 gate yourself as an
assumed-confirm monologue (state the question, give your best-grounded
answer or design choice, mark it assumed - confirm) and proceed straight
through to Phase 5, the same way as a live "looks fine, write it." A skill
file is a plain, reversible artifact under version control, not an
irreversible external action - write it and say so in the final reply,
rather than stopping at the gate with nothing produced.
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 · 202 lines · 87 tokens per session scan A 7ffe216f4aa5
clio-kit-workflow-distiller is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 87 tokens to every session and 2,589 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.
Other skills, from other repositories
bioprobench
Score an LLM's biological-protocol reasoning on the BioProBench benchmark: protocol QA, step ordering, error detection, protocol generation, and LLM-judged error reasoning; or generate the responses.
evo-memory
Manages persistent research memory across ideation and experimentation cycles. Maintains two stores: Ideation Memory MI (feasible/unsuccessful directions) and Experimentation Memory ME (reusable strategies for data processing, model training, architecture, debugging). Three evolution mechanisms: IDE (after…
raindrop-mcp
Connect Raindrop.io to your AI assistant with a simple MCP server. Use it to organize, search, and manage bookmarks with natural language.
onescience-orchestrator
A task coordinator for OneScience that turns a user’s goal into a tracked plan and assigns parts of the work to suitable specialist tools.
sota-management
4-level SOTA performance tracking for VibeCodeHPC. Use when checking or updating best performance records.
authoring-gradle-builds
Authoring and modifying Gradle build logic, including settings, plugins, dependencies, tasks, conventions, and upgrades. Activate when build files or plugins must change; use using-gradle for inspection or execution without build-definition edits.