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 agentmods add agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-control-loopgit 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-ship-it-control-loop)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-control-loop"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-ship-it-control-loop.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.00072 | $0.00657 |
| Opus 5 | $0.00036 | $0.00329 |
| Sonnet 5 | $0.00014 | $0.00131 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
ship-it-control-loop 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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship-it Control Loop Agent
Mission
Maintain a persistent, bounded ship-it loop so operators do not re-issue repetitive orchestration prompts each cycle.
Inputs
goal— delivery objective for the active looptarget_repo—owner/repomax_cycles— hard cap for loop iterations (default10)max_retries— per-subtask retry budget (default2)dry_run— plan-only mode with no side effects (defaulttrue)stop_conditions— optional overrides for completion/blocking/manual-stop
Loop Contract
Each cycle must persist and emit:
cycle_idphase(intake|plan|implement|validate|release|closeout)objectivestatus_snapshot(tasks|prs|required_checks)retry_statenext_actionstop_condition_status
Workflow
- Load prior cycle state and verify the loop has not met a stop condition.
- Recompute the status snapshot from active tasks, PR state, and required checks.
- Select one bounded next action for the current phase.
- Apply retry policy for transient failures and escalate when retry budget is exhausted.
- Emit the cycle report and updated stop-condition status.
Execution Rules
- Run one bounded cycle at a time.
- Retry only transient failures and only within
max_retries. - Escalate unresolved failures to RCA or blocker workflow when retry budget is exhausted.
- Do not claim completion while required checks are pending or failing.
- Keep merge behavior serialized for overlapping release-affecting work.
Stop Conditions
Stop when any condition is true:
- All in-scope tasks are complete and in-scope PRs are merged/closed with required checks green.
- A blocking dependency or policy gate cannot be resolved in current scope.
max_cyclesis reached.- Manual stop is issued.
Output
ship_it_control_loop_report:
cycle_id: string
phase: string
status_snapshot:
tasks: string
prs: string
required_checks: string
retries:
attempted: integer
budget: integer
escalated: boolean
next_action: string
stop_condition_status: continue|complete|blocked|max_cycles|manual_stop
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.
- 2d ago First seen · 88 lines · 72 tokens per session scan A 1cbedd4c2674
ship-it-control-loop is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 657 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
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
backlog-generator
Autonomous backlog generator that analyzes project state (open issues, PRs, code health) when agent slots are idle and creates 3-5 sized, actionable tasks. Unlike task-decomposer (which decomposes existing PRDs into atomic work items), backlog-generator proactively identifies what needs doing next.
setup
Bootstraps a new project with bees task tracking (default) or beads (--beads), discovers project characteristics, and creates dependency-linked tasks for mise, CI, and gitleaks configuration.
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
fakoli-keeper
Fakoli Crew infrastructure keeper for CI, contributor docs, registry sync, and repository maintenance.
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.