Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jmylchreest/aidenpx agentmods add skills/jmylchreest/aide/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/jmylchreest/aide/autopilot)<a href="https://agentmods.dev/skills/jmylchreest/aide/autopilot"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/autopilot/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/jmylchreest/aide/autopilot"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/autopilot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.00842 |
| Opus 5 | $0.00008 | $0.00421 |
| Sonnet 5 | $0.00003 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
autopilot 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autopilot Mode
Recommended model tier: smart (opus) - this mode handles complex multi-step tasks
Full autonomous execution mode. The agent keeps working until all tasks in the todo list are verified complete. No stopping early, no partial results.
Activation
Type naturally:
autopilot build me a web app
autopilot fix all failing tests
autopilot refactor the auth module
Or explicitly set the mode:
aide state set mode autopilot
How It Works
When autopilot mode is active:
- The persistence hook intercepts stop signals
- If incomplete tasks exist in the todo list, the agent is re-prompted to continue
- The agent keeps working through its task list
- Auto-releases when ALL tasks are complete (terminal state)
- Safety cap: releases after 20 iterations even if tasks remain
Platform Behavior
| Platform | Mechanism |
|---|---|
| Claude Code | Stop-blocking — prevents the AI from ending the conversation early |
| OpenCode | Re-prompting — session.prompt() is called on idle to keep going |
Task Tracking
Autopilot relies on the todo list to determine completeness:
- Has incomplete tasks → Block stop, continue working
- All tasks complete → Auto-release, allow stop
- No tasks exist → Generic reinforcement (verify your work)
When to Use
Autopilot mode is ideal for:
- Multi-step implementations — "autopilot implement the user dashboard"
- Fixing all test failures — "autopilot fix all failing tests"
- Complete refactors — "autopilot refactor all error handling to use Result types"
- Migration tasks — "autopilot migrate all components to the new API"
- Build fixes — "autopilot make the build pass"
When NOT to Use
Avoid autopilot for:
- Exploratory tasks — "investigate why X happens" (no clear completion criteria)
- Design work — Use the
designskill instead (needs human input) - Tasks requiring human judgment — Autopilot continues based on automated checks
- Parallel work — Use
swarmmode instead for decomposed parallel stories
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.
- 10d ago First seen · 113 lines · 16 tokens per session scan A cc2499b1162d
autopilot is a skill published in the GitHub repository jmylchreest/aide (17 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 842 once invoked, about $0.0001 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
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
bundle-safety
Bundle transform safety — minification variant selection, consumer-constraint verification, identifier preservation, and namespace re-export coverage for build output.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…