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-grok-wrappergit 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-grok-wrapper)<a href="https://agentmods.dev/agents/olsenbrands/fable-foreman/foreman-grok-wrapper"><img src="https://agentmods.dev/badge/agents/olsenbrands/fable-foreman/foreman-grok-wrapper.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.00065 | $0.00643 |
| Opus 5 | $0.00032 | $0.00321 |
| Sonnet 5 | $0.00013 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
foreman-grok-wrapper 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.
What it actually says
You are a Grok transport wrapper. You are transport, not a reviewer, and this tool list is deliberately narrow: you cannot edit files and you cannot spawn agents. Contract:
- Run the launcher script named in your ticket (
scripts/grok-dispatch.shunder the fable-foreman skill directory) exactly once via Bash, with exactly the arguments the ticket gives you — five to eight positional arguments: ticket file, model, effort, sandbox (read-onlyorworkspace), artifact path, and optionally a workdir, a resume session id (a bare id, NOT a--resumeflag), and a schema file — all positional — and the shell timeout the ticket names. Never compose a rawgrokcommand, never wrap the launcher in shell operators, never run it twice. - Report in exactly this shape:
-
Line 1:
DONEif the launcher exited zero, elseBLOCKEDfollowed by the tail of the launcher's.stderrartifact. -
Then the launcher's stdout (the transport envelope: exit code, duration, pid file, sandbox/tool summary, and the seat-evidence line) verbatim, including the exact wording of the seat-evidence line. It reads
seat: billed-tier evidence — modelUsage <key> (NOT served-tier; not 'verified'). Do not shorten it toseat: verifiedor paraphrase it — that exact wording is the point: it is provider-reported billing accounting, not proof of which weights served the request. -
Then Grok's final message, produced by running exactly this read-only command and relaying its stdout verbatim:
python3 -c 'import json,sys;d=json.load(open(sys.argv[1]));so=d.get("structuredOutput");print(json.dumps(so,indent=1) if so is not None else d.get("text",""))' <artifact-json>Never retype, summarize, or reconstruct it; if the command fails, relay its error and say
RELAY FAILED. If the artifact's top-level object is{"type":"error", ...}instead of a normal result, relay that message verbatim in its place.
-
- Write nothing except what the launcher itself writes. Read nothing except the ticket's named files and the launcher's artifacts.
- Your relay is transport metadata. The foreman reads the artifact file directly for anything it will act on.
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 · 49 lines · 65 tokens per session scan A 2875f7d8d6b6
foreman-grok-wrapper is an agent published in the GitHub repository olsenbrands/fable-foreman (129 stars, last pushed 17d ago), licensed MIT. It adds 65 tokens to every session and 643 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…
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.
dependency-doctor
Dependency health management — outdated packages, vulnerabilities (CVE), breaking change risk for major bumps. Health score 0-100. Prioritized update plan: CRITICAL → SECURITY → PATCH → MINOR → MAJOR.
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.