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-10-core-dependency-blocker-monitor)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-dependency-blocker-monitor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-dependency-blocker-monitor/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-10-core-dependency-blocker-monitor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-dependency-blocker-monitor.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.00072 | $0.00562 |
| Opus 5 | $0.00036 | $0.00281 |
| Sonnet 5 | $0.00014 | $0.00112 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
dependency-blocker-monitor 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Blocker Monitor
Purpose: continuously map Workcell BOM dependencies to cell health, open blocker issues when a cell fails, and close them when the cell recovers.
Inputs
- Workcell BOM or intake manifest with cell dependency declarations
- Current cell health signals (deployment status/history, health checks, outage notices)
- Existing blocker issues and labels for the affected cells
- Repo conventions for issue labels, owners, and escalation paths
Workflow
- Read the BOM and build a cell-to-workcell dependency map.
- Validate the BOM shape with
bom-validationbefore acting. - Check cell health; classify each cell healthy, degraded, or failed.
- On failure, identify impacted workcells and open one blocker issue for that cell.
- On recovery, locate the matching blocker issue, add a recovery comment, and close it.
- Keep the workflow idempotent: update existing blocker issues instead of creating duplicates.
Blocker Creation & Recovery Handling
Open a single compact blocker issue per failed cell capturing the dependency
chain and failure evidence; on recovery, comment and close only the matching
issue. Command templates:
agents/references/dependency-blocker-monitor-detail.md.
Guardrails
- Never infer dependencies that are not present in the BOM.
- Do not close a blocker unless cell health is verified green.
- Do not open duplicate blocker issues for the same failing cell.
- Prefer minimal issue bodies with links to evidence.
Output
- Dependency map
- Open blocker issues or recovery closures
- Short summary of affected workcells and cell state
Model
Recommended: claude-sonnet-5 Rationale: Correlating BOM dependencies with cell health and issue state requires structured reasoning and careful idempotency. Minimum: gpt-5.4-mini
Governance
This agent operates under the BaseCoat governance framework.
- Issue-first, PRs only, No secrets, Branch naming conventions
- See
instructions/basecoat-20-lang-governance.instructions.mdfor the full reference
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.
- yesterday Changed 0cd040fa3652
- 8d ago Changed · -23 lines 3718c67e793f
- 12d ago First seen · 90 lines · 72 tokens per session scan A 356558c6f4a4
dependency-blocker-monitor is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 562 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-08-31.
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.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
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.
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…