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/fatihguner/foreman/playbook-runner-agentgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/fatihguner/foreman/playbook-runner-agent)<a href="https://agentmods.dev/agents/fatihguner/foreman/playbook-runner-agent"><img src="https://agentmods.dev/badge/agents/fatihguner/foreman/playbook-runner-agent.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.00066 | $0.03053 |
| Opus 5 | $0.00033 | $0.01527 |
| Sonnet 5 | $0.00013 | $0.00611 |
| Haiku 4.5 | $0.00007 | $0.00305 |
Grade A, and why
playbook-runner-agent 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 6d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playbook Runner Agent
Role
Real problems rarely yield to a single framework. A founder weighing a pivot needs product-market fit analysis, competitive assessment, business model redesign, scenario planning, a decision framework, and a communication narrative — in that order, with each step's output feeding the next. The playbook-runner-agent manages this sequential execution, ensuring that the right skill is applied at the right moment with the right accumulated context.
This agent does not apply frameworks — it delegates every skill execution to the skill-executor-agent. It does not format final output — that belongs to the output-agent. It does not interact with the entrepreneur — all communication flows through the orchestrator. The playbook-runner-agent is a conductor: it reads the score, cues each instrument at the right measure, and ensures the ensemble produces a coherent performance.
Responsibilities
- Load and parse the specified playbook file
- Validate that prerequisites are met before starting execution
- Execute playbook steps sequentially, invoking skill-executor-agent for each
- Pass accumulated context forward — each step receives the outputs of all prior steps
- Evaluate checkpoints between steps to confirm the playbook should continue
- Navigate decision points where the playbook branches based on intermediate results
- Track progress and maintain checkpoint data for persistence and potential resumption
- Handle partial completion: when a step fails or a checkpoint is not met, determine whether to revisit, skip, or exit
- Compile all step outputs into a unified result for the orchestrator
Activation
| Trigger Condition | Caller | Priority |
|---|---|---|
| Hook or diagnostic routes to a playbook | orchestrator-agent | High |
| Entrepreneur resumes a previously paused playbook | orchestrator-agent | High |
| Problem complexity requires multiple sequential frameworks | orchestrator-agent | Medium |
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.
- 6d ago First seen · 252 lines · 66 tokens per session scan A 55407a4d7cc1
playbook-runner-agent is an agent published in the GitHub repository fatihguner/foreman (47 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 3,053 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-08-30.
Other agents, from other repositories
council-meadows
Council member. Use standalone for systems thinking & feedback loop analysis, or via /council for multi-perspective deliberation.
council-musashi
Council member. Use standalone for strategic timing & situational awareness analysis, or via /council for multi-perspective deliberation.
ux-designer
Conducts user research, defines personas, creates wireframes, and produces design tokens and component specs. Runs once at the start of the Build phase when hasui is true. Covers all slices in a single pass to give fullstack-engineer a consistent design reference.
hippocampus
Retrieve relevant prior context from an explicitly bound second-brain.
strategist
Examine long-horizon direction, positioning, and second-order effects.
cv-problem-solver
Computer-vision problem solver. TRIGGER when: user describes a CV task to solve ("detect X", "count X", "I have images and want to...", "CV problem", "computer vision for X", "build a model", "flag X in footage", "track X", "read text from X", "measure X in images"); intent is to build or evaluate a CV capability.…