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-rollout-basecoat)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-rollout-basecoat"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-rollout-basecoat.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.00080 | $0.00628 |
| Opus 5 | $0.00040 | $0.00314 |
| Sonnet 5 | $0.00016 | $0.00126 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
rollout-basecoat 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roll Out BaseCoat Agent
Purpose: onboard a repository or portfolio to BaseCoat using safe, repeatable release practices.
Inputs
- Target repository or portfolio
- Preferred installation channel
- Approved BaseCoat version or release tag
- Any enterprise constraints such as restricted egress or internal mirrors
- Consumer update mode, approval policy, and allowed SemVer bumps
Process
- Choose the distribution channel: Windows artifact, macOS or Linux artifact, or CLI download.
- Pin the release version instead of using a moving branch.
- Install or upgrade BaseCoat into the target repository from within an isolated
worktree on a uniquely-named
chore/basecoat-upgrade-<ref>-<timestamp>branch so the primary working tree stays clean. - Validate that required files and bootstrap paths are present.
- Complete the delivery lifecycle: commit the refreshed payload (conventional
message +
Co-authored-by: Copilottrailer), push the branch, open a PR, then remove the worktree and prune. Never leave the upgrade uncommitted. If the consumer is already at the target build (nothing to commit), skip the PR, remove the worktree, delete the unused branch, and report "already up to date." Seeskills/rollout-basecoat/references/delivery-lifecycle.mdfor the exact change-path and no-change-path commands. - Record the installed version and update instructions for future upgrades.
- For recurring updates, install the distributed workflow and configure
.basecoat.ymlupdates. Keep notify plus required approval as defaults; automatic mode must defer to GitHub branch protection and required checks.
Expected Output
- Selected rollout method
- Installed or planned version
- Validation steps
- Upgrade guidance
Model
Recommended: gpt-5.3-codex Rationale: Repeatable rollout steps with well-defined validation — speed and cost matter most Minimum: gpt-5.4-mini
Reference
Distribution channels/commands, the post-install validation checklist, and the
rollout-failure issue-filing template:
agents/references/rollout-basecoat-detail.md.
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 · 69 lines · 80 tokens per session scan A af6321688191
rollout-basecoat is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 80 tokens to every session and 628 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
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
commit
Runs the auto-commit skill.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.