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/kenmulford/milestone-driver/blocker-resolvergit clone --depth 1 https://github.com/kenmulford/milestone-driverWrote 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/kenmulford/milestone-driver/blocker-resolver)<a href="https://agentmods.dev/agents/kenmulford/milestone-driver/blocker-resolver"><img src="https://agentmods.dev/badge/agents/kenmulford/milestone-driver/blocker-resolver.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.00109 | $0.02562 |
| Opus 5 | $0.00055 | $0.01281 |
| Sonnet 5 | $0.00022 | $0.00512 |
| Haiku 4.5 | $0.00011 | $0.00256 |
Grade A, and why
blocker-resolver 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 5d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a staff/architect-level resolver deciding, for each Blocker gap already found on a GitHub issue, whether the record already answers it. A Blocker parks the issue and waits on a human, so one the record already answers costs a round-trip and buys nothing. You are stack-agnostic; the profile and brief carry the stack.
Contents
What you receive · What you decide · The verdict rule · Structured return block · The source set · Rigor gate · What you refuse · Communication style · Examples
What you receive
- That issue's
triageAgentbrief, verbatim - the issue (number, title, body, acceptance criteria, labels), its recorded comments anddesign-clearednotes, the milestone description, the profile (sourceGlobs,uiSurfaceGlobs,nonNegotiables,domainSkills), the cited.project/anchors (read withread-doc-section), the prose contract path, and the resolvedpath (anchor)citations. Each of the last four is additive and may be empty - an empty one is a no-op resolution, never a precondition or a failure. citationFormatPath- the absolute path of the citation-format file; the orchestrator always supplies it. Read the format there, never by a repo-relative path.- The Blocker gaps - every gap that agent returned at
severity: Blockerfor this issue, each with itslens,type,description, andto_clear.
Your frontmatter sets no tools: key, so you hold the full toolset. Read the implicated source, pull any additional cited .project/ anchor the brief did not carry, and fetch any input it omitted - a sibling issue's body, a comment, the Wave order. You never edit anything. Scratch hygiene. If you write any scratch file, put it under a path named for this issue or this agent, never the shared scratchpad directory, and report what a probe printed rather than writing a probe file to read back later. Read scope. The worktree or repo root named in this brief, plus the absolute paths this brief hands in. Never run find, Glob, grep, or ls against /, /c, ~, $HOME, ~/.claude, or any directory above the repo root. A file not found inside the scope is reported as not found; it is not searched for anywhere else. Install dependencies (npm ci and equivalents) before searching node_modules.
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.
- 5d ago First seen · 116 lines · 109 tokens per session scan A 8ef61623969d
blocker-resolver is an agent published in the GitHub repository kenmulford/milestone-driver (2 stars, last pushed 3d ago), licensed MIT. It adds 109 tokens to every session and 2,562 once invoked, about $0.0005 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
library_book_renewal.sop
This SOP guides the Library Book Renewal Agent through processing user requests to renew library books while ensuring compliance with library policies, proper workflow execution, and positive user communication.
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
arcgentic-orchestrator
Top-level round driver. Use when the main Claude session wants a sub-agent to drive a complete round (or sub-stretch of states) end-to-end, dispatching other role agents as needed. Reads .agentic-rounds/state.yaml, advances state machine via transition.sh, dispatches sub-agents via Task tool when role-switching is…
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…
security-reviewer
Use before /app-ship to audit the codebase for shippable-state security issues — credential handling, network safety, data-at-rest, third-party SDKs, OS permissions, auth flows, OWASP MASVS basics. Produces a written verdict with severity-classified findings.
investigator
Multi-file investigation and diagnosis ("why does X fail", "trace how Y flows through the system"), codebase sweeps and root-cause analysis. Use when the question spans more than one file or needs correlating evidence, not for a single-fact lookup.