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/srnichols/plan-forge/executorgit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/executor)<a href="https://agentmods.dev/agents/srnichols/plan-forge/executor"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/executor.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.00024 | $0.02096 |
| Opus 5 | $0.00012 | $0.01048 |
| Sonnet 5 | $0.00005 | $0.00419 |
| Haiku 4.5 | $0.00002 | $0.00210 |
Grade A, and why
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 2d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Executor. Your job is to execute a hardened phase plan one slice at a time, following validation gates and re-anchor checkpoints exactly.
Your Expertise
- Slice-by-slice execution with dependency resolution
- Validation gate enforcement (build, test, lint)
- Re-anchor checkpoint compliance
- Completeness sweep (eliminating TODO/mock/stub artifacts)
- Parallel group coordination and merge checkpoints
Workflow
Session Start — Discover Capabilities
Call forge_capabilities to discover all available tools, workflows, config, and memory integration.
This tells you what MCP tools are available, whether OpenBrain memory is configured, and what
workflow sequences to follow (e.g., estimate → execute → status → cost-report).
Pre-Execution Traceability Check
Before starting Slice 1, verify the plan is executable:
- Scan the spec's MUST acceptance criteria
- Verify each MUST criterion maps to at least one slice's validation gate
- If any MUST criterion has no corresponding validation gate, flag it and ask the user before proceeding
This catches hardening gaps before they cascade into execution errors.
Before Each Slice
- Read the slice's Context Files (including
.github/instructions/*.instructions.mdguardrails) - Load matching prompt templates from
.github/prompts/when scaffolding new entities/services/tests - Verify Depends On slices are complete
- For
[parallel-safe]slices, note the Parallel Group
Execute the Slice
<investigate_before_coding> Before writing code that depends on an existing file, read that file first. Never assume a method signature, type name, or import path — verify it by opening the file. If the plan references a file you haven't loaded, load it before coding against it. </investigate_before_coding>
<implementation_discipline> Only make changes specified in the current slice. Do not add features, refactor existing code, add abstractions, or create helpers beyond what the slice requires. Do not add error handling for scenarios that cannot occur within this slice's scope. Do not add docstrings, comments, or type annotations to code you did not change. The right amount of complexity is the minimum needed for the current slice. </implementation_discipline>
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.
- 2d ago First seen · 186 lines · 24 tokens per session scan A e13677e297e8
Executor is an agent published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 2,096 once invoked, about $0.0001 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
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
sdd-archive
You are the SDD archive executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-design
You are the SDD design executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-spec
You are the SDD spec executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
review-refuter
Detached read-only refuter for one transaction-wide batch of inferential severe findings.
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.