What is pituitary CLAUDE.md?

A project instruction file for Pituitary, a tool that checks whether software specifications, documentation, and code remain aligned. It defines the project's architecture, coding standards, source-of-truth rules, and workflow.

It is for guiding implementation and documentation work in the Pituitary project, including its local-file inputs, Markdown documents, SQLite index, command-line interface, and optional MCP wrapper.

It gives coding agents consistent rules for working in the Pituitary repository. It reduces conflicting edits and keeps generated instruction files tied to the canonical AGENTS.md file.

How nantobv/pituitary configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nantobv/pituitary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nantobv/pituitary/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/nantobv/pituitary

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/nantobv/pituitary/claude-md/github.svg)](https://agentmods.dev/instructions/nantobv/pituitary/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/nantobv/pituitary/claude-md"><img src="https://agentmods.dev/badge/instructions/nantobv/pituitary/claude-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/nantobv/pituitary/claude-md"><img src="https://agentmods.dev/badge/instructions/nantobv/pituitary/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 644 This file is loaded in full into every session.

When invoked 644 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00644	$0.00644
Opus 5.5	$0.00258	$0.00258
Sonnet 5.5	$0.00129	$0.00129
Haiku 4.5	$0.00064	$0.00064

Measured 2mo ago against content hash 25869485c6eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pituitary CLAUDE.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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

pituitary GEMINI.md — 92% identical, 1 lines differ

CLAUDE.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generated from AGENTS.md. Edit AGENTS.md, then rerun scripts/sync-ai-docs.sh --write. If this file conflicts with AGENTS.md, AGENTS.md wins.

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.

Coding Standards

Read README.md and ARCHITECTURE.md before deep implementation work. Use the active GitHub issues for backlog and priority context.
If you touch core write paths or repo governance, also read docs/development/repo-governance.md.
Treat repository docs as the primary source of truth; keep GitHub issues aligned with them rather than the reverse.
Prefer small, reversible changes and deterministic tooling over hand-maintained generated state.
Keep outputs machine-readable where the architecture expects JSON-first behavior.

Architecture Rules

First ship is CLI-first. Keep the CLI as the required transport and do not make core behavior depend on MCP, even though the repo also ships an optional MCP wrapper.
Scope is local filesystem only: spec.toml + body.md bundles, Markdown docs, SQLite, and sqlite-vec.
The repo ships CI for fmt, readiness, test, and vet validation, but GitHub- or vendor-specific reporting integrations remain out of scope.
Spec and doc analysis come before code-compliance features.
Canonical contract decisions live in ARCHITECTURE.md; update repo docs and GitHub issues together when those contracts change.

Read the full file on GitHub · 50 lines

Changes

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.

2mo ago First seen · 50 lines · 644 tokens per session scan A 25869485c6eb

Subscribe to this mod's changes

pituitary CLAUDE.md is an instructions file published in the GitHub repository nantobv/pituitary (22 stars, last pushed 5mo ago), licensed MIT. It adds 644 tokens to every session, about $0.0026 per session on Opus 5.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.

ai-tools cli developer-tools documentation mcp

pituitary CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pituitary CLAUDE.mdnantobv/pituitary	Instructions file	22	5mo ago	MIT	A	644	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

pituitary: Instructions file for Claude Code