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 skills add ivegamsft/basecoat --skill delivery-autopilotgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/delivery-autopilot)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/delivery-autopilot"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/delivery-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.00085 | $0.00476 |
| Opus 5 | $0.00043 | $0.00238 |
| Sonnet 5 | $0.00017 | $0.00095 |
| Haiku 4.5 | $0.00009 | $0.00048 |
Grade A, and why
delivery-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 4d 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
Delivery Autopilot Skill
Use this skill to run approve-once automation loops with deterministic helper scripts and workflow handoff contracts.
Inputs
repo:owner/repoissue_numberand/orpr_numberrequired_checks: list of required check contextsdry_run: boolean
Script Pipeline
scripts/delivery-autopilot/evaluate-status.ps1scripts/delivery-autopilot/execute-merge.ps1scripts/delivery-autopilot/build-escalation-payload.ps1
All scripts support deterministic -DryRun mode and JSON outputs for workflow handoff.
Integration Path
These three workflows are optional downstream consumers of this skill's output
files, not preconditions the skill depends on: each is an opt-in templates
class entry in scripts/configure-downstream-workflows.ps1, not installed by
default. If a workflow below isn't installed, its output JSON file simply goes
unconsumed -- no delivery-autopilot script fails or blocks on its absence.
basecoat-pr-auto-merge-executor.ymlconsumes merge-readiness posture.post-merge-release-chain.ymlconsumes merge results to dispatch release gate workflow.automation-stuck-state-watchdog.ymlconsumes escalation payload data when SLA stages stall.
Output Contract
test-results/delivery-autopilot/status-summary.jsontest-results/delivery-autopilot/merge-result.jsontest-results/delivery-autopilot/escalation-payload.json
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 52 lines · 85 tokens per session scan A df35eab000ef
delivery-autopilot is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 476 once invoked, about $0.0004 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
github-workflows
Use when doing GitHub work end-to-end: auth, repository setup, issue triage, PR implementation, code review, CI monitoring, merge/release, and fallback REST workflows.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.