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/oakandfeather/ai-assisted-coding-governance/agents-mdgit clone --depth 1 https://github.com/oakandfeather/ai-assisted-coding-governanceWrote 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/oakandfeather/ai-assisted-coding-governance/agents-md)<a href="https://agentmods.dev/instructions/oakandfeather/ai-assisted-coding-governance/agents-md"><img src="https://agentmods.dev/badge/instructions/oakandfeather/ai-assisted-coding-governance/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.1 | $0.10238 | $0.10238 |
| Opus 5 | $0.05119 | $0.05119 |
| Sonnet 5 | $0.02048 | $0.02048 |
| Haiku 4.5 | $0.01024 | $0.01024 |
Grade A, and why
ai-assisted-coding-governance 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 yesterday.
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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Version: 1.32 · Last reviewed: 2026-09-01 · Active client: none (internal repository)
Guidance for AI agents working in this repository — the source repo for the AI-assisted coding governance package. This repo applies its own rules to itself.
⚠️ Mandatory rules
Before any task, read and follow core-rules.md — the non-negotiable base that applies to every task (secrets, data, correctness, licensing, provenance, safe agentic actions, compliance, stop-and-ask, client overrides). Then read the module for your task: writing-rules.md before producing or editing documents and content — including documentation about code, such as READMEs, API references, and runbooks (factual grounding, citations, confidentiality, voice fidelity, accessible documents, verified documentation) — the module that applies to nearly everything here, since this repository is Markdown — and coding-rules.md before writing, editing, or running code (dependencies, security, testing, accessibility), which covers the PowerShell scripts in scripts/. If anything below conflicts with these, the stricter rule wins. Load them in one pass before you start reading this repository's code or content — not after you have picked an approach. For a non-trivial task that means core-rules.md, the task module above, the active client's profile (below — none in this repo), and the matching craft companion — writing-patterns.md for content, coding-patterns.md for code; scale that set to the blast radius the way core-rules.md's own checklist does — a typo doesn't earn four files. A rule reached after the work is shaped is too late to shape it. Load means open the file with your file-reading tool — a link you have not opened has not loaded.
Work the way agent-workflow.md describes (work loop, ask-vs-proceed-vs-object boundary, verification, structured hand-off, bounded iteration and adversarial self-review, economy of effort, subagent delegation). Read writing-patterns.md before writing or editing a non-trivial document — which is most work here — and coding-patterns.md before writing or editing non-trivial code; apply their quality patterns. Where craft meets safety, safety and correctness win.
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.
- yesterday Changed · +2 lines · +191 tokens per session c1840cd4401e
- 5d ago First seen · 212 lines · 10,047 tokens per session scan A 31c258dfbb29
ai-assisted-coding-governance AGENTS.md is an instructions file published in the GitHub repository oakandfeather/ai-assisted-coding-governance (2 stars, last pushed 3d ago), licensed MIT. It adds 10,238 tokens to every session, about $0.0512 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
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).
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.
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.
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).