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/output-commands)<a href="https://agentmods.dev/commands/fatihguner/foreman/output-commands"><img src="https://agentmods.dev/badge/commands/fatihguner/foreman/output-commands.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.00000 | $0.00957 |
| Opus 5 | $0.00000 | $0.00478 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
output-commands 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 7d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Commands
Reformatting, exporting, and comparing analysis outputs from skills and playbooks.
/format [audience]
Reformat the most recent output for a different audience. Content stays identical -- structure, emphasis, vocabulary change per the target template.
Syntax: /format <audience>
| Parameter | Required | Values | Description |
|---|---|---|---|
audience |
Yes | investor, board, team |
Maps to the corresponding output template. |
Examples:
> /format board
SWOT --> board. Strategic Position Q1 2026: Distribution moat via 3 enterprise
partnerships ($2.1M ACV). Threats: 2 funded competitors in mid-market.
Actions: 1) 3 AE hires Q2. 2) Competitive response review.
> /format team
Unit Economics --> team. Action Plan: CAC payback 14mo (target <12), 2.1% trial
conversion. Product: onboarding redesign Apr 15. Marketing: $8K/mo reallocation.
Sales: 30-min onboarding calls for trials >$500 MRR.
> /format investor
Competitive Landscape --> investor. Series A: 12+ players, no dominant platform.
Edge: real-time compliance + automated reporting, 2 patents. Moat: 4-6mo switching cost.
Related: /export, /compare
Errors: No output: No recent analysis. Run a skill or playbook first. Bad value: Unknown audience. Available: investor, board, team.
/export [format]
Export the most recent output as a file. Filename: {skill}_{date}.{ext}.
Syntax: /export <format>
| Parameter | Required | Values | Description |
|---|---|---|---|
format |
Yes | md, pdf, html, txt |
Output file format. |
Examples:
> /export md
swot-analysis_2026-03-26.md (4.2 KB) ready.
> /export pdf
unit-economics_2026-03-26.pdf (12.1 KB) ready.
> /export html
competitive-landscape_2026-03-26.html (8.7 KB) ready.
> /export csv
Unknown format: "csv". Available: md, pdf, html, txt.
Related: /format, /compare
Errors: No output: No recent analysis. Run a skill or playbook first. Bad format: Unknown format. Available: md, pdf, html, txt. Failure: Export failed. Try a different format or check /status.
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.
- 7d ago First seen · 90 lines · 0 tokens per session scan A 2f4f44f1e638
output-commands is a command published in the GitHub repository fatihguner/foreman (47 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 957 tokens. 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 commands, from other repositories
arckit.customize
Copy plugin templates to project for customization.
arckit.search
Search across all project artifacts by keyword, document type, or requirement ID.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.