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 skills add ivegamsft/basecoat --skill dependency-blocker-monitoringgit 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/skills/ivegamsft/basecoat/dependency-blocker-monitoring)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/dependency-blocker-monitoring"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/dependency-blocker-monitoring/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/skills/ivegamsft/basecoat/dependency-blocker-monitoring"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/dependency-blocker-monitoring.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.00064 | $0.00364 |
| Opus 5 | $0.00032 | $0.00182 |
| Sonnet 5 | $0.00013 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
dependency-blocker-monitoring 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 8d 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
Dependency Blocker Monitoring Skill
Use this skill to keep Workcell dependency blockers synchronized with cell health.
Workflow
- Read the workcell BOM and validate the dependency shape.
- Build a cell-to-workcell impact map from the declared dependencies.
- Check the current cell health signal for each dependency cell.
- Create blocker issues when a cell fails.
- Resolve the matching blocker issue when the cell recovers.
Issue Lifecycle
Use one open blocker issue per failed cell.
gh issue list --state open --label blocker --search "<cell-name>"
If no blocker exists for the failed cell, create one with the failure evidence and impacted workcells. If a blocker already exists, update the existing issue instead of creating a duplicate.
On recovery, add a short closure comment, then close the issue after the health check is green.
Guardrails
- Do not invent dependencies that are not in the BOM.
- Do not close blockers without a verified recovery signal.
- Keep the issue body short and link to the authoritative evidence.
- Reuse existing BOM and factory state artifacts when they are present.
Output
- Dependency impact map
- Open or closed blocker issues
- Short recovery summary
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 51 lines · 64 tokens per session scan A 350bd4df90b2
dependency-blocker-monitoring is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 364 once invoked, about $0.0003 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 skills, from other repositories
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
env-setup-assistant
Expert guide for setting up development environments including IDE configuration, tooling, dependencies, and developer onboarding. Use when bootstrapping new projects or standardizing team environments.
meeting-processor
Process meeting transcripts and Notion meeting notes into structured organizational records, action items, and memory updates.
mailroom-acknowledgement-sweep
Route unrouted mail and chase what nobody acknowledged.
asset-inventory-reconciliation
Reconcile recorded against observed assets.
committed-schedule-coordination
Keep committed schedule and reality in step.