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/nantobv/pituitary/agents-mdgit clone --depth 1 https://github.com/nantobv/pituitaryWrote 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/nantobv/pituitary/agents-md)<a href="https://agentmods.dev/instructions/nantobv/pituitary/agents-md"><img src="https://agentmods.dev/badge/instructions/nantobv/pituitary/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.01267 | $0.01267 |
| Opus 5 | $0.00633 | $0.00633 |
| Sonnet 5 | $0.00253 | $0.00253 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
pituitary 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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Canonical AI policy for this repo. If model-specific mirrors exist, generate them from this file.
Project
Pituitary is a consistency governance tool that keeps specifications, documentation, and code aligned. It builds a temporal, confidence-weighted governance graph from spec bundles and docs, then runs overlap, drift, compliance, impact, and freshness analysis against it. The current repo is focused on local filesystem inputs, Markdown docs, SQLite-backed indexing, a CLI-first interface, an optional MCP wrapper, and repo CI validation.
Org-wide policy (nantobv-shared)
The bullets in this section are the org-wide floor for AI agents working on
any nantobv project. They are vendored verbatim from
nantobv/.github/AGENTS.shared.md;
refresh the local copy with
scripts/sync-agents-shared.sh.
Project-specific rules live in each repo's own AGENTS.md sections outside
this block.
Planning and approval
- Read the repo's
AGENTS.md,README.md, and the documents they point at before deep implementation work. - For non-trivial changes, propose the plan (files you expect to touch and why, approach, rationale) and wait for approval before writing code. Plan mode satisfies this; a dedicated planning skill or brainstorming ceremony is not required.
- Show diffs and wait for approval before committing or pushing, unless the
user has invoked a publish workflow (e.g.
cpprrm) that explicitly authorizes commit/push for the current task and no stronger repo or security gate applies.
Git hygiene
- Run
git statusandgit diff --minimalbefore any commit. - Stage explicit paths. Never use
git add .. - Keep unrelated local files out of commits, including local
.ccd.tomland harness work directories unless the task explicitly targets them.
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.
- 6d ago First seen · 114 lines · 1,267 tokens per session scan A 84bc0eb41051
pituitary AGENTS.md is an instructions file published in the GitHub repository nantobv/pituitary (22 stars, last pushed 3mo ago), licensed MIT. It adds 1,267 tokens to every session, about $0.0063 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
Skill_Seekers CLAUDE.md
Instructions for yusufkaraaslan/Skill_Seekers, covering claude.md, project overview, essential commands, required before running tests or cli (src/ layout) and run all tests (never skip - all must pass before commits).
Skill_Seekers AGENTS.md
Instructions for yusufkaraaslan/Skill_Seekers, covering agents.md - skill seekers, project overview, key capabilities, setup and with dev tools (pytest, ruff, mypy, coverage).
documcp copilot-instructions.md
Instructions for tosin2013/documcp, covering documcp ai coding agent instructions, architecture essentials, mcp server design (src/index.ts), tool implementation pattern and knowledge graph memory (src/memory/).
docusaurus-plugin-copy-page-button AGENTS.md
AGENTS.md instructions for portdeveloper/docusaurus-plugin-copy-page-button, covering agents.md, project overview, key architecture, core components and plugin architecture.
Bamboo CLAUDE.md
Claude Code instructions for VolcanoEngineering/Bamboo, covering claude.md, what this repo is, cold-start order for claude, claude-shaped operating notes and when you're working on this repo.
better-code CLAUDE.md
Claude Code instructions for hculap/better-code, covering claude.md, project overview, development commands, test a plugin locally and install from marketplace (for users).