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 agentmods add skills/paraskakis/skills/agent-ready-cli-auditnpx skills add paraskakis/skills --skill agent-ready-cli-auditgit clone --depth 1 https://github.com/paraskakis/skillsWrote 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/paraskakis/skills/agent-ready-cli-audit)<a href="https://agentmods.dev/skills/paraskakis/skills/agent-ready-cli-audit"><img src="https://agentmods.dev/badge/skills/paraskakis/skills/agent-ready-cli-audit.svg" alt="Measured on agentmods" 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 | $0.00121 | $0.03225 |
| Opus 5 | $0.00060 | $0.01613 |
| Sonnet 5 | $0.00024 | $0.00645 |
| Haiku 4.5 | $0.00012 | $0.00323 |
Grade A, and why
agent-ready-cli-audit scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. **Find the install path**: identify the documented one-line install (brew, npm/npx, pipx/uvx, curl script, releases page) and whether it would work in a clean environment. How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-Ready CLI Audit
Overview
Use this skill to evaluate an existing CLI against the Agent-Ready CLI Checklist.
Audit mode is evidence-first. Inspect docs/code and run the CLI where possible. Do not replace missing evidence with imagined best practices.
The audit asks:
Would a coding agent get stuck trying to discover, authenticate, inspect, plan, act, verify, and recover?
Included References
references/agent-ready-cli-checklist-v2.md— canonical checklist and scoring rubric. Use it as the source of truth for scoring.
Scope and Routing
Triggering is defined in the frontmatter description. In scope: evidence-based review of an existing CLI, repo, or docs. Out of scope: greenfield command design (use agent-ready-cli-spec) and implementation (use agent-ready-cli-build).
Inputs
| Input | Required | Notes |
|---|---|---|
| Target CLI | Yes | Installed command name, repo path, npm/PyPI/Homebrew package name, or docs URL — any one is enough. |
| Focus workflows | No | Specific workflows the user cares about most. |
| Safe environment | No | Whether mutating commands may be exercised. Default: no — read-only commands only. |
| Credentials | No | Env var names for auth'd commands. Never ask the user to paste secrets into the conversation; ask for names of env vars already set in the shell. |
The target can arrive as a command name, a path on disk, a package name, a docs URL, or a GitHub repo. Never go looking on disk and report what you found there.
Gather inputs once, then run unattended. If the target CLI is named in the request, skip questions entirely — proceed straight to Step 0 with the table's defaults for everything else.
Only if the target is missing, ask once, like a person. Do not announce that a directory is empty, do not cite these instructions:
Which CLI should I look at? A command name, a repo path, a package name, or a docs URL — whatever you've got.
Also: is it safe to run commands that change things, or should I stick to read-only? (Read-only is my default.)
What ships with it
1 file 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.
- 4d ago First seen · 254 lines · 121 tokens per session scan A e0ed2d82cefe
agent-ready-cli-audit is a skill published in the GitHub repository paraskakis/skills (41 stars, last pushed 1mo ago), licensed MIT. It adds 121 tokens to every session and 3,225 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…