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/duthaho/skillhub/autopilotnpx skills add duthaho/skillhub --skill autopilotgit clone --depth 1 https://github.com/duthaho/skillhubWrote 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/duthaho/skillhub/autopilot)<a href="https://agentmods.dev/skills/duthaho/skillhub/autopilot"><img src="https://agentmods.dev/badge/skills/duthaho/skillhub/autopilot.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.1 | $0.00095 | $0.02590 |
| Opus 5 | $0.00048 | $0.01295 |
| Sonnet 5 | $0.00019 | $0.00518 |
| Haiku 4.5 | $0.00010 | $0.00259 |
Grade C, and why
autopilot 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 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
`pyproject.toml`, CI config). **No test suite?** Don't refuse — schedule a How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
autopilot — the whole loop, one yes
/autopilot <task> — run the full pipeline, stop at an open PR
/autopilot <task> --merge — also merge, once every gate is green
/autopilot resume <change> — pick up a crashed, aborted, or parked run
/autopilot status — report runs in flight under out/dev/
Answer one question: what would come back if this task were handed to a careful team and nobody watched over their shoulder? The other coding skills put a human at every gate; this one replaces those gates with the things that made them work — fresh-context review, diverse critique, and a test suite as the arbiter — and reserves the human for exceptions. Human on the loop, not in it: you sign once, you get a PR, and anything the pipeline couldn't settle honestly comes back parked, not guessed.
The charter — one yes, spelled out
The invocation is the consent. Echo this before running, then don't ask again:
- WILL: read anything in the repo; write state under
out/dev/<slug>/; create GitHub issues labeledautopilot; create and push branchesautopilot/<slug>/*; open one PR; comment on and close its own issues; with--merge, merge that PR once every gate is green. - NEVER: push to the default branch directly, force-push, rewrite history, delete branches or issues it didn't create, weaken a test to get green, or touch anything outside this repo.
Auto mode — how the other skills run here
Autopilot drives map, feature, and done in auto mode, a shared
convention: every approval gate becomes a self-approval on the record —
the decision and its reason are appended to log.md instead of asked — and
every verdict that would need a human becomes a PARK. The skills' own
rules (task sizing, TDD, tripwires, never-weaken-tests) are unchanged; only
the waiting is removed. In auto mode the run never calls a tool that
stops to wait on a human — AskUserQuestion first among them (waiting on
sub-agents or commands is fine): with nobody watching, such a call isn't a
question, it's a deadlock. A decision only a human can settle is parked
with the decision spelled out — never waited on, never guessed.
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 · 202 lines · 95 tokens per session scan C bb47515900a6
autopilot is a skill published in the GitHub repository duthaho/skillhub (9 stars, last pushed 12d ago), licensed MIT. It adds 95 tokens to every session and 2,590 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.