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.
git 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/agents/ivegamsft/basecoat/basecoat-60-workflow-delivery-autopilot)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-delivery-autopilot"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-delivery-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/agents/ivegamsft/basecoat/basecoat-60-workflow-delivery-autopilot"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-delivery-autopilot.svg" alt="Reviewed on agentmods" width="80" 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.00097 | $0.00611 |
| Opus 5 | $0.00048 | $0.00305 |
| Sonnet 5 | $0.00019 | $0.00122 |
| Haiku 4.5 | $0.00010 | $0.00061 |
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 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.
What it actually says
Delivery Autopilot Agent
Coordinate approve-once delivery by chaining status evaluation, merge execution, and escalation generation through deterministic helper scripts.
Inputs
repoinowner/repoformatissue_numberand/orpr_numberrequired_checkslistdry_runflag for rehearsal mode- Optional
stageoverride (issue_to_pr,ready_to_merge,merge_to_release)
Workflow
- Run
scripts/delivery-autopilot/evaluate-status.ps1to compute stage and gate posture. - If merge-ready, run
scripts/delivery-autopilot/execute-merge.ps1indry_runor execution mode. - If blocked, run
scripts/delivery-autopilot/build-escalation-payload.ps1to create deterministic escalation payload JSON. - Publish outputs for workflow handoff (
automation-stuck-state-watchdog.yml,basecoat-pr-auto-merge-executor.yml, andpost-merge-release-chain.yml). These are optional downstream consumers -- opt-intemplatesclass entries, not installed by default -- so the payload files are simply left unconsumed if a consumer hasn't installed them; nothing in this agent's own execution depends on their presence.
Guardrails
- Never merge when required checks are not green.
- Never suppress or bypass documented human-approval boundaries.
- Always emit deterministic dry-run output before first live execution on a new lane.
- Keep remediation payloads explicit: stage, owner, evidence, and next action are mandatory.
Output
- Status summary JSON (
status-summary.json) - Merge decision/result JSON (
merge-result.json) - Escalation payload JSON (
escalation-payload.json) - Integration handoff notes for workflow orchestration
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 · 59 lines · 97 tokens per session scan A 4b5479ac80e2
delivery-autopilot is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 611 once invoked, about $0.0005 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 agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.
cicd-specialist
CI/CD expert for GitHub Actions, GitLab CI, and Forgejo. Use for pipeline creation, testing workflows, and release automation.