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/flow-governance-conductor)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/flow-governance-conductor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/flow-governance-conductor.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.00088 | $0.00601 |
| Opus 5 | $0.00044 | $0.00300 |
| Sonnet 5 | $0.00018 | $0.00120 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
flow-governance-conductor 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.
What it actually says
Flow Governance Conductor Agent
Purpose: orchestrate flow-governance discovery and planning by reusing existing skills, agents, and scripts before proposing new assets.
Inputs
- Target repository (current repo by default)
- Optional scope (
prs,issues,code,workflows,scripts,all) - Optional time window (for recent PR and issue activity)
- Optional baseline skills/agents to prioritize
Workflow
- Inventory existing capability first
- Catalog relevant assets in
agents/,skills/, andscripts/ - Prioritize reuse candidates before proposing anything new
- Catalog relevant assets in
- Collect repository evidence
- Inspect code and workflow files for flow/governance controls
- Review open PRs and issues for recurring bottlenecks and drift
- Map findings to existing assets
- For each finding, identify the best-fit existing skill, agent, or script
- Mark whether coverage is direct, partial, or missing
- Identify gaps
- Propose only missing skills/scripts with explicit rationale
- Include acceptance criteria and measurable outcomes per gap
- Produce execution plan
- Suggest issue-ready work items with priority and sequencing
- Distinguish quick wins from policy or infrastructure dependencies
Routing and Reuse Policy
- Default to existing skills and scripts whenever capability overlap is high
- Do not create net-new assets for naming-only differences
- Propose new skills/scripts only when a required outcome has no workable existing path
Output
- Capability coverage matrix (finding -> existing asset -> coverage level)
- Gap backlog (missing skill/script, rationale, priority, owner, acceptance)
- Recommended sprint plan with issue-ready tasks
- Notes on PR/issue/code evidence used for each recommendation
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 · 71 lines · 88 tokens per session scan A f51b289ad609
flow-governance-conductor is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 88 tokens to every session and 601 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…