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/cookys/autopilot/onboardnpx skills add cookys/autopilot --skill onboardgit clone --depth 1 https://github.com/cookys/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/cookys/autopilot/onboard)<a href="https://agentmods.dev/skills/cookys/autopilot/onboard"><img src="https://agentmods.dev/badge/skills/cookys/autopilot/onboard.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.00213 | $0.02329 |
| Opus 5 | $0.00106 | $0.01164 |
| Sonnet 5 | $0.00043 | $0.00466 |
| Haiku 4.5 | $0.00021 | $0.00233 |
Grade A, and why
onboard 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard — calibrate autopilot to a consuming project
Turns a repo with no autopilot config into one that speaks its own build commands, coverage thresholds,
doc layout, and ecosystem-standalone dispatch chains. The deterministic half is scripted (detect +
scaffold); the judgment half is yours (map this project's domain to skills, derive doc⇄code drift
domains, name security surfaces). The golden reference output is the hand-built ~/projects/hangar-bridge/.claude/.
Premise: ecosystem-standalone. The scaffolded chains default to autopilot-only (the assumed baseline is autopilot +
codeforge+mnemos, no third-party plugins).superpowersis added only as an explicit, commented fallback when the project actually has it installed. Never scaffold a superpowers-first default.
Available Scripts (prefer over LLM judgment for the mechanical half)
| Script | Role |
|---|---|
scripts/project-detect.js |
Detect (pure read → JSON): package manager, commands (+lint_is_noop), per-package coverage thresholds, doc convention (doc/ vs docs/), workspace/packages, default_branch, protected-path candidates, project paths, installed plugins. Run it FIRST; it owns every mechanical fact. |
scripts/scaffold-config.js |
Scaffold (mechanical write): copies+fills the config set into <target>/.claude/, fills detected values, writes autopilot-only chains when superpowers=false, merge-safely pins CLAUDE_CODE_ENABLE_TODO_TOOLS=1 into .claude/settings.json (task tools are gated off on 5-era models since CC 2.1.233 — without the pin every dev-flow forcing function silently no-ops; an explicit existing value is respected), and updates .gitignore to exclude runtime state while KEEPING *-config.md tracked. Idempotent; --force to clobber a hand-edit; --dry-run to preview. |
Workflow
1. Detect (mechanical — run the script, read the JSON)
node <autopilot>/scripts/project-detect.js <target-repo> | tee /tmp/onboard-detect.json
Read the JSON. Sanity-check it against the repo: does package_manager, doc_dir, the coverage table, and
default_branch match reality? default_branch is only emitted when the target IS the git top-level; if it
is null or wrong (e.g. the repo's origin/HEAD isn't set), note the canonical branch for step 4. Do not
re-derive these facts by hand — the detector owns them.
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.
- 5d ago First seen · 126 lines · 213 tokens per session scan A 2a004f00da44
onboard is a skill published in the GitHub repository cookys/autopilot (11 stars, last pushed yesterday), licensed MIT. It adds 213 tokens to every session and 2,329 once invoked, about $0.0011 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-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…