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/ocentra/ocentra-enforcer/agents-mdgit clone --depth 1 https://github.com/ocentra/ocentra-enforcerWrote 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/ocentra/ocentra-enforcer/agents-md)<a href="https://agentmods.dev/instructions/ocentra/ocentra-enforcer/agents-md"><img src="https://agentmods.dev/badge/instructions/ocentra/ocentra-enforcer/agents-md.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.00339 | $0.00339 |
| Opus 5 | $0.00169 | $0.00169 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
ocentra-enforcer 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 3d 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
Enforcer Agent Router
doctrine: "the harness is the reviewer of first resort; AI and humans may write code, the harness decides if it is structurally acceptable"
route_first: "enforcer route / mcp__enforcer__route before opening detailed rule docs; smallest scope: files -> crate/package -> diff -> workspace"
pre_done_gate: "enforcer check mutation-risk --root . --base origin/main --head HEAD; enforcer verify --root . --profile strict"
banned: "bypass comments, skipped tests, broad waivers, re-export shims, rule downgrades to force a gate to pass"
The harness is the reviewer of first resort.
AI and humans may write code. The harness decides whether code is structurally acceptable. Human review begins after mechanical policy, compiler/type/lint gates, architecture gates, tests/proofs, dependency/security gates, and local/CI parity pass.
Call enforcer route / MCP mcp__enforcer__route before opening detailed
rule docs. Use the smallest route: exact files, crate/package, diff, then
workspace only when needed.
Before claiming work complete, run the scoped enforcer gate for the changed surface. If policy-critical files changed, run:
enforcer check mutation-risk --root . --base origin/main --head HEAD
enforcer verify --root . --profile strict
Do not add bypass comments, skipped tests, broad waivers, re-export shims, or rule downgrades to make a gate pass.
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.
- 3d ago First seen · 33 lines · 339 tokens per session scan A 62764b8ce9af
ocentra-enforcer AGENTS.md is an instructions file published in the GitHub repository ocentra/ocentra-enforcer (0 stars, last pushed 8d ago), licensed MIT. It adds 339 tokens to every session, about $0.0017 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.