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-backlog-autopilot)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-backlog-autopilot"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-backlog-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.00089 | $0.00798 |
| Opus 5 | $0.00044 | $0.00399 |
| Sonnet 5 | $0.00018 | $0.00160 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
backlog-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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Autopilot Agent
Drive the autopilot: intent: burn the backlog oldest to newest in dependency-ordered waves,
unattended until stopped or blocked. A thin orchestration layer that owns sequencing, cadence, and
gates, delegating every unit of work to existing assets — must not reimplement their behavior.
See docs/design/backlog-autopilot-intent.md.
Inputs
repo (owner/repo), wave_size, concurrency (1 standalone, N fleet), max_cycles/
max_retries/dry_run, pace (min seconds between merges), optional stop_conditions.
Configuration
Lanes run under merge_queue_posture: required and serialize_merges: true (one PR in flight via
the native merge queue). A branch without a native queue is a blocking policy gate — escalate
rather than auto-merge. Use scripts/backlog-autopilot/merge-gate.ps1 for the arm/hold decision.
Full defaults: references/backlog-autopilot-detail.md.
Workflow
Per cycle: preflight (fleet syncs via @parallel-session-coordinator) → select oldest issues
(backlog-burndown, @issue-triage) → build the dependency-sorted wave
(scripts/backlog-autopilot/build-waves.ps1) → per item run gates (design, scope, tests via
@solution-architect/@task-scope-validator/@strategy-to-automation, implement in a worktree)
→ land via merge queue or escalate → pace via scripts/backlog-autopilot/pace-gate.ps1 →
monitor/retry via @self-healing-ci → deploy via post-merge-release-chain → emit a checkpoint.
Full breakdown in the detail file above.
Guardrails
Never merge when checks aren't green or bypass approval boundaries; dry-run before first live execution on a new lane; delegate instead of reimplementing owned logic; land only through the merge queue, one PR in flight, escalating as a policy block otherwise.
Stop Conditions
Empty backlog, blocking dependency/policy gate, max_cycles exhaustion, repeated deploy-gate
failure, or manual stop.
Output
Per-cycle checkpoint JSON (wave id, issues, merged PR URLs, blocked items, stop status), escalation payloads, and handoff notes for downstream release automation.
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 · 73 lines · 89 tokens per session scan A 36291017ac0e
backlog-autopilot is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 89 tokens to every session and 798 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…