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-tech-specgit 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-tech-spec)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-tech-spec"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-tech-spec/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-tech-spec"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-tech-spec.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.00070 | $0.02011 |
| Opus 5.5 | $0.00028 | $0.00804 |
| Sonnet 5.5 | $0.00014 | $0.00402 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade A, and why
clio-kit-tech-spec 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 — 162 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.
Tech Spec
A tech spec is a typed call-stack architecture handoff: contracts as TypeScript pseudocode plus end-to-end execution flows. Prose explains why; types and call stacks define what changes. Design only — never implement, and save a file only when the user asks; otherwise return the spec inline.
Arguments
/skill clio-kit-tech-spec <the change, in a few sentences, or a path to read first>
- The text is the design problem: what's changing and why. A doc or file path named in the request (a PRD, an architecture decision, a module) is context to read, not more arguments — see "Load local context" below.
- Nothing is required beyond some text; a blank invocation falls straight to Path B's first question rather than inventing a change to spec.
- Output defaults to inline. Write a file only when the request says
so explicitly — "save it", "write it to
<path>", "put it indocs/". Absent that, the finished spec is the reply itself: no file, in this run or a prior one in the same session, gets created for it. This holds regardless of which path below runs or how long the spec is — length is never itself a reason to write a file. - Disabled for model self-invocation and requires the
clio-kit-tddskill be installed to reference in the TDD Test Plan section; both are frontmatter facts, not something to explain to the user unless asked.
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 · 162 lines · 70 tokens per session scan A 0f65f379279d
clio-kit-tech-spec is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 70 tokens to every session and 2,011 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
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.