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-archifygit 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-archify)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-archify"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-archify/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-archify"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-archify.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.00113 | $0.02235 |
| Opus 5.5 | $0.00045 | $0.00894 |
| Sonnet 5.5 | $0.00023 | $0.00447 |
| Haiku 4.5 | $0.00011 | $0.00224 |
Grade A, and why
clio-kit-archify 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 — 187 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.
Archify
Create a self-contained interactive HTML diagram from a small typed JSON
specification. This library package contains Clio instructions; the renderer is
an independently installed upstream Archify v2.16.0 package. Before authoring,
locate its directory containing bin/archify.mjs, schemas/ and examples/.
If unavailable, ask the operator to prepare that upstream renderer; do not claim
that installing this instruction package installed it. Below, <renderer> is
that verified directory, and renderer-relative schema/example paths refer to it.
The renderer needs Node 18 or later; ordinary rendering then needs no network.
Fast authoring path
- Choose
architecture,workflow,sequence,dataflow, orlifecyclefrom the question. When ambiguous, runnode <renderer>/bin/archify.mjs guide "<scenario>" --json. - Read one matching schema in
schemas/,schemas/common.schema.json, and one matching example inexamples/. Read only those files. The example supplies field shape, never facts: author new stable ids, domain wording, and layout. New workflows useschema_version: 2. - Write the candidate JSON as the very next action. Do not plan coordinates
in prose. Start with one clear main path, short side branches, sparse
labels, and at most 12 primary nodes. Set
meta.quality_profileto"showcase"unless the user asks for a densestandardmap. Start with automatic routes and labels; addvia,channelX,channelY, orlabelAtonly when a diagnostic asks for one, and at most one per repair. - Validate after every edit and immediately before delivery:
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 · 187 lines · 113 tokens per session scan A a3bbbbfd949e
clio-kit-archify is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 113 tokens to every session and 2,235 once invoked, about $0.0005 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
nano-banana
Generate professional presentation slides and high-quality illustrations using Gemini image generation API (Nano Banana 2), with interactive browser-based review and iterative editing. Full workflow: content planning conversation → slidesplan.json → batch image generation → review with feedback → targeted slide…
figure-style
Correctness and legibility checklist for publication figures, plus a matplotlib sidecar. Load before plotting anything and call applyfigurestyle() (role-mapped font ladder, outward ticks, frameless legends, 300-dpi saves, CJK-safe fonts). Covers data fidelity, label budgets, axis/colour/type rules, chart choice by…
custom-theme
Author a Wisp custom theme CSS file that uses documented tokens and import constraints. Use when the user wants a custom look, hide the paragraph lead bar, restyle chat Markdown, override colors, or import a stylesheet under Settings → Appearance.
interactive-ui
Ask the user to pick an option, or render GitHub data as an interactive UI panel.
bio-data-visualization-color-palettes
Select colormaps and qualitative palettes for scientific figures using perceptual-uniformity, color-vision-deficiency safety, and luminance-monotonicity criteria. Covers Crameri scientific colormaps, viridis/cividis/magma, Okabe-Ito categorical, ColorBrewer, and the rainbow/jet critique. Use when choosing palettes for…
screenshots
Advanced UI analysis and interaction through pixel-level reasoning to solve complex interaction problems, locate hard-to-find elements, verify visual states, and debug layout/rendering issues. Use as needed after UI Mapper inspection when advanced reasoning or non-standard views are required.