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.
git 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/commands/fatihguner/foreman/stage)<a href="https://agentmods.dev/commands/fatihguner/foreman/stage"><img src="https://agentmods.dev/badge/commands/fatihguner/foreman/stage/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/commands/fatihguner/foreman/stage"><img src="https://agentmods.dev/badge/commands/fatihguner/foreman/stage.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.00005 | $0.00150 |
| Opus 5.5 | $0.00002 | $0.00060 |
| Sonnet 5.5 | $0.00001 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
stage 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 1mo 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.
This is a copy
89% identical to abort — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Foreman /stage
Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/command-guides/meta-commands.md and execute only /stage with the user's arguments: $ARGUMENTS.
Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result.
Use the command map in catalog.json to recommend only registered commands.
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.
- 1mo ago First seen · 14 lines · 5 tokens per session scan A 1a81fd499ffe
stage is a command published in the GitHub repository fatihguner/foreman (59 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 150 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to abort, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
frappe-gameplan
Treat the task as Frappe Gameplan work.
pod
Create a Wakeflow pod for parallel work, or close one after its branch has been merged or abandoned.
to-issues
Create one Linear issue per slice from an existing scope.json. Run standalone to (re)create issues without rerunning the full Plan phase. Falls back to docs/issues.md if Linear MCP is unavailable.
sdlc-plan
Phase 1 — Plan. Runs product-manager grill-me interview + slice decomposition, then publishes PRD and creates issues. Invokes exactly 1 agent.
arckit.backlog
Generate prioritised product backlog from ArcKit artifacts - convert requirements to user stories, organise into sprints.
arckit.story
Generate comprehensive project story with timeline analysis, traceability, and governance achievements (project).