Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add WinterDDo/claude-code-skill-autopilot/plugin install skill-autopilotWrote 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/winterddo/claude-code-skill-autopilot/whats-new)<a href="https://agentmods.dev/skills/winterddo/claude-code-skill-autopilot/whats-new"><img src="https://agentmods.dev/badge/skills/winterddo/claude-code-skill-autopilot/whats-new/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/winterddo/claude-code-skill-autopilot/whats-new"><img src="https://agentmods.dev/badge/skills/winterddo/claude-code-skill-autopilot/whats-new.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.00062 | $0.00442 |
| Opus 5 | $0.00031 | $0.00221 |
| Sonnet 5 | $0.00012 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
whats-new 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 8d 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
What's newly possible
Two sources, both local. Speak the user's language, lead with benefit, never list for listing's sake.
New commands (after a knowledge-base update)
Read ${CLAUDE_PLUGIN_ROOT}/knowledge/commands.json and playbooks.json. Compare against what the user has actually seen used (counters in ~/.claude/command-autopilot/state.json). Pick the 2-3 entries most relevant to how this user works (their evidence shows what they do) and present each as: what it is → what it does for YOU → the one-line way to try it. Mention the version it arrived in.
Installed-but-unused skills
Read ~/.claude/command-autopilot/skills-index.json; cross-reference with state.json skill counters. Skills with zero invocations are dormant value the user already owns. Pick the 1-2 most relevant to their evidence profile: "You installed X — it can ... — next time you ..., I'll use it automatically."
High-leverage commands the user has never used
The biggest gap for most users is the powerful commands they don't know exist. Read ${CLAUDE_PLUGIN_ROOT}/knowledge/commands.json + playbooks.json, cross-reference state.json command counters, and surface the high-leverage ones with zero usage — Workflow orchestration, parallel /fork, /goal, /loop, /background. For each: what it is → what it does for THEIR kind of work → the one-line way to try it. This is the "you can't ask for what you don't know exists" gap — lead with it.
Rules
Max 5 items total per run. Relevance over completeness; the rest stays for next time. End with: "Ask again any time — this list updates itself."
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.
- 8d ago First seen · 21 lines · 62 tokens per session scan A a085bdce60ec
whats-new is a skill published in the GitHub repository WinterDDo/claude-code-skill-autopilot (6 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 442 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
architect
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design".
backend
This skill should be used when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs".
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.
frontend-design
Use when user asks to build a web component, page, or application, or when the task involves frontend design, HTML/CSS generation, or UI layout. Applies specific rules for typography, OKLCH color, layout, motion, interaction, and UX writing to produce distinctive, production-grade interfaces that avoid generic AI…
harness-export
Use when user invokes /harness-export or wants to save their current harness-kit plugin setup to a shareable harness.yaml file. Detects installed skills, collects source info, and writes the config in Harness Protocol v1 format. Do NOT use for importing or restoring a harness — use /harness-import instead.
lineage
Use when user invokes /lineage with a column name (optionally qualified with table/schema). Also triggers on "trace this column", "where does X come from", "what reads from Y table". Traces column-level data lineage through SQL, Kafka, Spark, JDBC, and ORM codebases. Produces a structured lineage path with confidence…