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 wyattowalsh/agents --skill skill-install-dry-run-plannergit clone --depth 1 https://github.com/wyattowalsh/agentsWrote 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/wyattowalsh/agents/skill-install-dry-run-planner)<a href="https://agentmods.dev/skills/wyattowalsh/agents/skill-install-dry-run-planner"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/skill-install-dry-run-planner/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/wyattowalsh/agents/skill-install-dry-run-planner"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/skill-install-dry-run-planner.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.00040 | $0.00485 |
| Opus 5.5 | $0.00016 | $0.00194 |
| Sonnet 5.5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
skill-install-dry-run-planner 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 1mo 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.
What it actually says
Skill Install Dry-Run Planner
Produce a maintainer plan from skills-sync dry-run evidence.
Scope: Dry-run planning only. Never run live apply installs from this skill.
Dispatch
| $ARGUMENTS | Action |
|---|---|
| Empty | Full dry-run plan for all harnesses |
--harness <name> |
Plan for one harness adapter |
--format json |
Machine-readable plan |
help |
Show phases, gates, and related runbooks |
Planned Phases
- Validate — run the repo validation command
- Dry-run JSON — run the skills-sync dry-run JSON command
- Review gaps — inspect
missing,unresolved, andskippedrows per harness - Optional smoke —
INSTALL_SMOKE=1temp-home phase (maintainer machine only) - Apply gate — human approval required before any
--apply
Also see skills/cross-agent-install-smoke/ and docs/runbooks/install-smoke.md.
Workflow
uv run python skills/skill-install-dry-run-planner/scripts/plan_dry_run.py
uv run python skills/skill-install-dry-run-planner/scripts/plan_dry_run.py --harness cursor --format json
Validation Contract
uv run python skills/skill-install-dry-run-planner/scripts/check.py
Critical Rules
- Default to dry-run; treat sync JSON as evidence, not authority over repo policy.
- Never auto-apply installs or run live
npx skills addfrom this skill. - Run phase 1 dry-run checks before recommending reconciliation.
- Gate temp-home smoke behind
INSTALL_SMOKE=1. - Document unresolved catalog rows instead of silently skipping them.
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.
- 1mo ago First seen · 59 lines · 40 tokens per session scan A 4bf7c67ab6a1
skill-install-dry-run-planner is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 485 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…