Borrowing it
Nothing to install: this file belongs to saski/arnesto. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saski/arnesto/main/.cursor/skills-cursor/autopilot/SKILL.mdgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/autopilot)<a href="https://agentmods.dev/skills/saski/arnesto/autopilot"><img src="https://agentmods.dev/badge/skills/saski/arnesto/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.00025 | $0.00826 |
| Opus 5 | $0.00013 | $0.00413 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autopilot
Your job is to get this PR to a merge-ready state: mergeable, required CI green, and every active unresolved comment triaged.
Operating loop
Refresh live PR state at the start of every pass (for example gh pr view and gh pr checks); never act on stale state from an earlier pass. Work blockers in strict priority order:
- Merge conflicts.
- Active unresolved comments and review threads.
- Failing CI.
Do not start CI work while an earlier blocker exists; conflict and comment fixes restart checks when pushed. If a pass finds no concrete action and checks are still running, watch them to completion (for example gh pr checks --watch) instead of polling in a tight loop, and do not invent work just because a pass came up empty. Read the PR diff only when a comment or CI failure needs code context.
1. Merge conflicts
Fetch the latest base branch from origin and resolve conflicts, preserving the intent and correctness of changes on your branch and the base branch. If intents genuinely conflict, abort the merge and ask for clarification.
2. Comments
Review active unresolved comments and review threads, including automated reviewers such as Bugbot. When fetching GitHub comments, filter out resolved threads first. Read only each comment body and the minimum location/URL needed to act on it; do not read the entire JSON output or other unnecessary payload data.
Decide fix, dismiss, or ask for each thread:
- Fix: the comment identifies a real issue within this PR's scope. Make the smallest safe change and reply referencing the fix.
- Dismiss: the comment is invalid or moot in context. Reply with the concrete reason; do not churn code to satisfy a noisy comment.
- Ask: never guess on security, privacy, auth, billing, data, migration, or concurrency comments, or when you need an answer to proceed. Surface these to the user immediately.
After a fix or dismiss reply, resolve the thread if you have permission; leave a thread open only when it is waiting on an answer.
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.
- 3d ago First seen · 49 lines · 25 tokens per session scan A 2f0fd7aebbca
autopilot is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 25 tokens to every session and 826 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-09-03.
Other skills, from other repositories
git-ai-search
Search and restore AI conversation context from git history.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
machinist
Use Machinist to create, assign, monitor, and resume software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, lifecycle labels, direct runs, or managed queue.
repo-sentinel
Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses. Triggers on: "push to GitHub", "make repo public", "open source this", "is this safe to push", "release audit", "secret leaks".
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).