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-fix-issuegit 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-fix-issue)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-fix-issue"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-fix-issue/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-fix-issue"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-fix-issue.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.00092 | $0.01605 |
| Opus 5.5 | $0.00037 | $0.00642 |
| Sonnet 5.5 | $0.00018 | $0.00321 |
| Haiku 4.5 | $0.00009 | $0.00161 |
Grade A, and why
clio-kit-fix-issue 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 — 127 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.
Fix Issue
Resolve one tracker issue: diagnose only as much as the issue leaves unknown, fix test-first, verify against the issue's own acceptance criteria. The skill ends with an uncommitted working tree and a completion report; committing, pushing, and PRs belong to ship.
See diagnosis and RCA for why-chain construction, root-cause documentation, and handling maintainer constraints.
Arguments
Arguments are passed in the user invocation message. Interpret them structurally from the prompt:
/skill:clio-kit-fix-issue [--repo owner/repo] <issue-number|issue-url>
Examples
/skill:clio-kit-fix-issue 42/skill:clio-kit-fix-issue #105/skill:clio-kit-fix-issue https://github.com/iowarp/clio-coder/issues/271/skill:clio-kit-fix-issue --repo acme/widgets 88
Positional Arguments
<issue-number|issue-url>: The GitHub issue identifier to fix.- Allowed forms:
- Pure integer:
42 - Hash-prefixed integer:
#42 - Full GitHub issue URL:
https://github.com/<owner>/<repo>/issues/<number>
- Pure integer:
- Required. If omitted, prompt the user for the issue number or URL.
- Allowed forms:
What ships with it
4 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 · 127 lines · 92 tokens per session scan A 3b89ba12fdb8
clio-kit-fix-issue is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 92 tokens to every session and 1,605 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
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
resolve-author-fix
Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
triage-issue
Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan. Triggers: triage, investigate bug, fix plan, root cause, file issue, bug report.
validate-fix
Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says "is this fixed?", or before closing an investigation.
refactoring-patterns
Systematic refactoring techniques, code smell elimination, pattern extraction, and legacy modernization.