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-clio-coder-testgit 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-clio-coder-test)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-clio-coder-test"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-clio-coder-test/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-clio-coder-test"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-clio-coder-test.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.00080 | $0.01996 |
| Opus 5.5 | $0.00032 | $0.00798 |
| Sonnet 5.5 | $0.00016 | $0.00399 |
| Haiku 4.5 | $0.00008 | $0.00200 |
Grade A, and why
clio-kit-clio-coder-test 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 — 163 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.
Clio Test
The root Node suite has a small required contract/process lane, an installed-package qualification lane, and explicit extended development regressions. Contract tests import source through tsx; CLI tests use the current built binary. Lint owns static import boundaries and library pins. Publication performs only an exact-candidate preflight after successful qualification.
For the question of whether a change may leave your machine (commit, push, or
PR), use clio-coder-dev. REQUIRED SUB-SKILL: clio-coder-dev for the
local-versus-contribution boundary.
Commands
npm run typecheck # tsc -p tsconfig.tests.json
npm run lint # Biome plus scripts/check-hygiene.ts
npm run skills:check # catalog pins and marketplace index
npm run test:file -- tests/contracts/<file>.test.ts
npm run build # tsup plus the codewiki asset
npm run test:file -- tests/smoke/<file>.test.ts # requires a current build
npm run test # required contracts and three process smoke files
npm run test:full # explicit extended root investigation
npm run test:web:full # explicit extended web investigation
pnpm --filter @iowarp/clio-coder-web verify # app types, lint, tests, build, browser
npm run ci # deterministic root gate
npm run ci:release # qualify clean committed source and exact installed tarball
npm run release:preflight # fast check of the unchanged qualified package
What ships with it
5 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 · 163 lines · 80 tokens per session scan A 464656259860
clio-kit-clio-coder-test is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 80 tokens to every session and 1,996 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
experiment-iterative-coder
Iterative code refinement through plan → code → evaluate → refine cycles. Runs lint checks (ruff), tests (pytest), and structured self-evaluation each cycle, then diagnoses failures and refines. Decomposes complex tasks into sequential phases, iterates up to 3 times per phase (10 total). Use when: the main agent…
verifying-compose-ui
Verifying Compose UI by rendering components or previews and inspecting the resulting images and state transitions. Activate for visual behavior that requires runtime rendering; use ordinary tests for nonvisual logic.
next-qa
Run one unattended iteration of the QUALITY-ASSURANCE loop — steward any in-flight QA PR, then build ONE queued qa issue (test infrastructure, unit tests, regression tests for known bugs) on a branch off auto-qa and open a PR that squash-merges on green CI. Adds tests and tooling only; never edits product source. Use…
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…
exploratory-testing
Run time-boxed exploratory testing against a web app to find bugs and inconsistencies. Use when asked to poke at an app, stress its forms, or hunt for edge cases.
generate-e2e-tests
Walk a flow in the browser and write end-to-end tests (Playwright, Cypress, etc.) that reproduce it. Use when asked to create e2e coverage for a user flow.