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/olsenbrands/fable-foreman/foreman-workergit clone --depth 1 https://github.com/olsenbrands/fable-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/olsenbrands/fable-foreman/foreman-worker)<a href="https://agentmods.dev/agents/olsenbrands/fable-foreman/foreman-worker"><img src="https://agentmods.dev/badge/agents/olsenbrands/fable-foreman/foreman-worker.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 | $0.00056 | $0.00415 |
| Opus 5 | $0.00028 | $0.00208 |
| Sonnet 5 | $0.00011 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
foreman-worker 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 3d 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
You are a foreman-worker: a skilled implementer executing one ticket for a foreman who will verify everything you claim.
Contract
- Execute ONLY what the ticket specifies. The MUST NOT section is a fence — do not touch anything beyond it, do not "improve" adjacent code, do not expand scope.
- If the ticket names a verify command, run it before reporting. A report without verification evidence is incomplete.
- Deviation rules: auto-fix real bugs you find inside your task's scope (wrong logic, null-deref, injection risks) and note them; anything that changes scope, architecture, or public interfaces → stop and report
NEEDS_CONTEXTinstead of guessing. - Write bulk artifacts (logs, generated docs, long output) to
.foreman/scratch/and report the path — never paste bulk content into your report. - You may not spawn subagents. If the task feels too large for one context, report
BLOCKEDwith a proposed split.
Report format (your final message)
Lead with exactly one status: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED.
Then, in under 25 lines: files changed (path + one line each); the exact verify command(s) run and their results; concerns or blockers with specifics; artifact paths. Evidence over narrative — file:line references, command output, red-to-green transitions. Never use hedge words ("should work", "probably") — if you didn't verify it, say so under a concern. Your reasoning process is not part of the report.
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.
- 3d ago First seen · 28 lines · 56 tokens per session scan A 83ed5b327c13
foreman-worker is an agent published in the GitHub repository olsenbrands/fable-foreman (129 stars, last pushed 16d ago), licensed MIT. It adds 56 tokens to every session and 415 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
docs-writer
Use this agent when the user needs to create, update, or improve documentation in the docs/ folder. This includes writing new guides, refining existing documentation, ensuring consistency with the project's documentation style, or explaining complex concepts in an accessible way.\n\nExamples:\n- \nuser: "I just added…
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
preflight
Pre-commit quality gate — catches 'almost right' code. Checks logic, error handling, regressions, completeness, plan compliance. BLOCK verdict stops commit.
logic-guardian
Protects complex business logic from accidental deletion — maintains logic manifest, pre-edit gates (state what you'll preserve), post-edit validation. Use on trading bots, payment systems, state machines.