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-ast-grepgit 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-ast-grep)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-ast-grep"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-ast-grep/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-ast-grep"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-ast-grep.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.00071 | $0.02227 |
| Opus 5.5 | $0.00028 | $0.00891 |
| Sonnet 5.5 | $0.00014 | $0.00445 |
| Haiku 4.5 | $0.00007 | $0.00223 |
Grade C, and why
clio-kit-ast-grep scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Cleaning up with `rm -rf`, or writing fixtures under `/tmp`; both are How it starts
The opening of the file, as written. The whole thing — 210 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.
ast-grep Structural Search
Translate a structural question into an ast-grep rule, prove the rule on a tiny example, then scan the real codebase. Never scan first: an untested rule that returns nothing tells you nothing.
Search only. Never use --update-all / -U / --rewrite; when matches need
changing, report them and edit through the normal edit tools.
Arguments
/skill clio-kit-ast-grep [--lang <language>] [--path <dir>] <structural question>
--lang: tree-sitter language name (javascript,typescript,python,rust,go, ...). Omit to infer from the files under--path.--path: directory or file to scan. Omit to scan the project source directory (src/when it exists, otherwise.).- Everything else is the question: what shape to find, what to exclude.
The five steps below are the plan; do not open a task list for them.
Examples:
/skill clio-kit-ast-grep find async functions that await but have no try/catch/skill clio-kit-ast-grep --lang python --path app/ find calls to open() outside a with block
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 · 210 lines · 71 tokens per session scan C b9fc856a108c
clio-kit-ast-grep is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 71 tokens to every session and 2,227 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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…
experiment-craft
Use this skill when the user wants to debug, diagnose, or systematically iterate on an experiment that already exists, or when they need a structured experiment log for tracking runs, hypotheses, failures, results, and next steps during active research. Apply it to underperforming methods, training that will not…
interacting-with-project-runtime
Interacting with a project's JVM runtime through the Kotlin REPL to execute focused probes against project classes and dependencies. Activate when behavior must be observed by running code; use using-gradle for build inspection or task execution.
using-gradle
Using Gradle MCP tools to inspect and run existing builds, including projects, tasks, properties, dependencies, and build results. Activate for Gradle build operation and diagnosis; use authoring-gradle-builds when the build definition itself must change.
browser-debug
Debug style issues and console errors in a running web app using the kogiQA browser tools. Use when asked to investigate a layout/overflow problem, a broken page, or to collect and fix console errors.
drive-mcpjam-playground
Drive an API Playground session through MCPJam's remote MCP tools or cloud CLI, inspect browser evidence, and hand the live session to its owner. Use for agent-driven MCP server debugging with a hosted browser.