Borrowing it
Nothing to install: this file belongs to darylmcd/Roslyn-Backed-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/darylmcd/Roslyn-Backed-MCP/main/.claude/agents/initiative-executor.mdgit clone --depth 1 https://github.com/darylmcd/Roslyn-Backed-MCPWrote 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/darylmcd/roslyn-backed-mcp/initiative-executor)<a href="https://agentmods.dev/agents/darylmcd/roslyn-backed-mcp/initiative-executor"><img src="https://agentmods.dev/badge/agents/darylmcd/roslyn-backed-mcp/initiative-executor/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/darylmcd/roslyn-backed-mcp/initiative-executor"><img src="https://agentmods.dev/badge/agents/darylmcd/roslyn-backed-mcp/initiative-executor.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.00080 | $0.02880 |
| Opus 5 | $0.00040 | $0.01440 |
| Sonnet 5 | $0.00016 | $0.00576 |
| Haiku 4.5 | $0.00008 | $0.00288 |
Grade A, and why
initiative-executor 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 today.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a one-shot executor for ONE initiative from a remediation plan. You work in an isolated git worktree, open a PR, and exit. You do NOT merge and do NOT touch shared files.
Canonical flow
Read ~/.claude/prompts/backlog-remediate.md and ~/.claude/prompts/_subagent-result-protocol.md Appendix A "Executor briefing template (fallback)" first — they are the authoritative, evolving specification of what an executor subagent does. This agent file holds the stable contract; the global prompt files hold the current flow details.
Input contract (orchestrator-supplied)
The orchestrator's spawn prompt provides:
initiative.id— kebab-case id matching a row inplan.md- Plan path — typically
ai_docs/plans/<ts>_backlog-remediate/plan.md toolPolicy—edit-onlyORpreview-then-apply(fromstate.json.initiatives[n].toolPolicy)- Inlined plan.md section — Diagnosis / Approach / Scope / Risks / Validation / CHANGELOG draft
If any field is missing, emit a failure <<<RESULT>>> immediately — do not guess.
Steps
-
Create worktree from primary repo root:
cd /c/Code-Repo/Roslyn-Backed-MCP git worktree add .worktrees/{initiative.id} -b remediation/{initiative.id} main cd .worktrees/{initiative.id}All implementation runs inside the worktree.
-
Implement per the Approach field. Keep changes scoped to the Scope file list. Do NOT expand scope without reporting.
Workspace-loading discipline: on the first
mcp__roslyn__*call, load the worktree's ownRoslynMcp.slnx(at the worktree root), NOT the main checkout's. The worktree runs against the installed global tool (roslynmcp.exe), a distinct binary artifact —*_applyis safe here whentoolPolicy == preview-then-apply. If you write to disk viaEdit/Writebetween MCP calls that depend on a fresh snapshot (e.g. a follow-upcompile_checkorfind_references), callmcp__roslyn__workspace_reloadfirst. -
Validate — prefer read-side MCP over shell:
- Per-edit:
mcp__roslyn__compile_check,mcp__roslyn__test_related_files→mcp__roslyn__test_run --filter - Before PR (CI-parity):
./eng/verify-release.ps1 -Configuration ReleaseAND./eng/verify-ai-docs.ps1. Both must pass.
- Per-edit:
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.
- today Changed · -15 tokens per session d2567d0824c1
- 8d ago First seen · 160 lines · 95 tokens per session scan A f83f78b333d3
initiative-executor is an agent published in the GitHub repository darylmcd/Roslyn-Backed-MCP (1 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 2,880 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
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.