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-cut-itgit 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-cut-it)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-cut-it"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-cut-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/iowarp/clio-kit/clio-kit-cut-it"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-cut-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.00076 | $0.01866 |
| Opus 5.5 | $0.00030 | $0.00746 |
| Sonnet 5.5 | $0.00015 | $0.00373 |
| Haiku 4.5 | $0.00008 | $0.00187 |
Grade A, and why
clio-kit-cut-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 — 148 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.
Cut It
Transform an existing plan into ordered execution slices that a coding agent
can run one at a time, leaving the build green after every slice. The output
is a SPRINT.md another agent can execute cold — no conversation context
required.
Arguments
cut it [<path to plan>]
There is no flag syntax; the trigger is conversational — "cut it", "slice
this plan", "turn this milestone into a sprint". A path the user names in
the same request (a specific PLAN.md, PRD.md, or milestones/*/prompt.md)
is the plan to slice; a path with no plan words near it, or a bare
destination like "write it to docs/SPRINT.md", is Step 3's output location,
not the input. When neither is named, Step 1 finds the plan and Step 3
writes to the repo-root default.
This run has no back-and-forth. ask_user is not registered in a headless
run, so any call is refused as an unregistered tool rather than answered.
The happy path here rarely needs a question at all — Step 1's "stop and say
so" for a missing or vague plan is already headless-safe, and Step 3's output
path defaults without asking. If several plans or milestones are plausible
candidates and the choice matters, do not stop on an open question: pick the
most recently modified or most specifically named one, state that choice and
the alternative you set aside, mark it assumed — confirm, and keep going in
the same turn. Do not end a turn on an unanswered question in ask_user or
in plain text.
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 · 148 lines · 76 tokens per session scan A 3cec486a55c5
clio-kit-cut-it is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 76 tokens to every session and 1,866 once invoked, about $0.0003 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
ambient-context-standup
Use when the user asks for a standup, daily update, status for a channel, or what to say they did. Drafts it from yesterday's Ambient Context summary and today's record so far, in the user's voice.
ambient-context-weekly-review
Use when the user asks for a weekly review, a week note, what happened this week, or what they spent the week on. Reads the last seven Ambient Context summaries and writes the review.
budget-tracking
Compute budget management with phase-based termination criteria. Use when checking budget, determining project phase, or making stop decisions.
next-qa-idea
Run one unattended IDEATION iteration of the quality-assurance loop — find the highest-value untested behavior in the codebase, judge it against the QA value bar, and file ONE locked qa issue specifying the test to write. Never writes code or tests; the next-qa skill builds from the queue this skill fills. Use when…
jira-driven-planning
A planning skill that turns Jira tickets and related Confluence documents into an implementation plan split across frontend, backend, and infrastructure work. Jira tracks work items, while Confluence stores team documentation.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.