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 instructions/visionforge-ou/foreman/agents-mdgit clone --depth 1 https://github.com/VisionForge-OU/foremanWhat 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.00641 | $0.00641 |
| Opus 5 | $0.00320 | $0.00320 |
| Sonnet 5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
foreman AGENTS.md 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 30 lines · 641 tokens per session scan A 8d7b0aa4aa46
foreman AGENTS.md is an instructions file published in the GitHub repository VisionForge-OU/foreman (447 stars, last pushed 2mo ago), with no licence file. It adds 641 tokens to every session, about $0.0032 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 instructions, from other repositories
deer-flow copilot-instructions.md
Copilot instructions for bytedance/deer-flow, covering copilot onboarding instructions for deerflow, 1) repository summary, 2) runtime and toolchain requirements, 3) build/test/lint/run - verified command sequences and a. bootstrap and install.
LeAgent AGENTS.md
Instructions for vixues/LeAgent, covering leagent development guidelines, project overview, architecture, execution topology (one kernel, many ingresses) and surface map (where things live).
sprawling CLAUDE.md
Instructions for 2youg1/sprawling: See AGENTS.md. It is the whole instruction set for this repository — the loop, what to read first, the five steps of one change, the rules a machine holds, and the language and commit conventions.
codex-acp-bridge AGENTS.md
Instructions for normahq/codex-acp-bridge, covering codex-acp-bridge — agents.md, development standards, quality gates (required), logging policy and bridge guardrails.
deckforge AGENTS.md
Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.
vant AGENTS.md
Instructions for dhaupin/vant, covering agents.md — vant agent guide, what is vant?, your job, brain router interface and middleware chain.