Borrowing it
Nothing to install: this file belongs to sponyhub/repo-foreman. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sponyhub/repo-foreman/main/AGENTS.mdgit clone --depth 1 https://github.com/sponyhub/repo-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/instructions/sponyhub/repo-foreman/agents-md)<a href="https://agentmods.dev/instructions/sponyhub/repo-foreman/agents-md"><img src="https://agentmods.dev/badge/instructions/sponyhub/repo-foreman/agents-md/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/instructions/sponyhub/repo-foreman/agents-md"><img src="https://agentmods.dev/badge/instructions/sponyhub/repo-foreman/agents-md.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.01352 | $0.01352 |
| Opus 5 | $0.00676 | $0.00676 |
| Sonnet 5 | $0.00270 | $0.00270 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade A, and why
repo-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 9d 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.
AGENTS.md — RepoForeman Contributor Contract
This file applies to the entire repository. It defines durable instructions for coding agents and contributors working on RepoForeman itself. It is not a template for consumer repositories and must not be injected into projects that use RepoForeman.
Start here
Before a broad or behavior-changing edit, read:
README.mdfor product scope, supported workflows, and public claims;CONTRIBUTING.mdfor contribution expectations;SECURITY.mdfor trust boundaries and vulnerability reporting;docs/architecture.mdfor the pipeline, isolation, recovery, and security model;- the relevant file under
docs/when changing configuration, artifacts, or release behavior.
RepoForeman is an early public beta. Keep changes focused, reviewable, and explicit about compatibility and security consequences.
Product invariants
- RepoForeman remains a local, deterministic delivery and governance layer around Codex CLI. Do not present it as a model provider, hosted service, OS security boundary, or replacement for native Codex Goal and subagent interfaces.
- Preserve restrictive defaults. Broader filesystem, network, environment, command, or host access must be explicit, visibly unsafe, and covered by tests and documentation.
- Keep the published runtime dependency-free unless a maintainer explicitly approves changing that contract. Prefer Node.js built-ins.
- Support the Node.js, operating-system, and Git worktree matrix documented in
package.jsonandREADME.md; verify that matrix manually before a release. - Keep every planning, worker, review, recovery, and verification loop bounded. Exhaustion must produce an explainable failure or partial result, never an unbounded retry cycle.
- Validate agent-produced structured data before it becomes executable state. A valid schema is necessary but does not prove factual correctness.
- Treat command and diff policy as defense in depth, not as a shell parser or sandbox. Do not weaken the documented trust boundary.
- Preserve baseline verification so pre-existing failures are not silently reported as regressions introduced by a run.
- Persist enough redacted state to explain and safely resume a run. Do not persist raw sensitive output by default.
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.
- 9d ago First seen · 90 lines · 1,352 tokens per session scan A cd2bfb2928a0
repo-foreman AGENTS.md is an instructions file published in the GitHub repository sponyhub/repo-foreman (1 stars, last pushed 6d ago), licensed Apache-2.0. It adds 1,352 tokens to every session, about $0.0068 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.