agentmods.dev

pituitary: Instructions file for Gemini CLI

GEMINI.md

pituitary GEMINI.md is an instructions file for Gemini CLI from nantobv/pituitary. It costs 660 tokens per session, scanned A, a copy of pituitary CLAUDE.md, MIT.

Repository instructions for Pituitary, a tool that checks whether specifications, documentation, and code stay aligned over time. It uses local files, Markdown documents, a SQLite database, a command-line interface, and an optional MCP wrapper.

In plain words
What is it for?
Implementing features, following the project architecture, maintaining governance checks, and keeping generated AI instruction files synchronized with the canonical AGENTS.md file.
Why use it?
It tells coding agents which documents and project rules are authoritative before they make changes. This helps prevent code, documentation, and repository policies from drifting apart.

Instructions file for Gemini CLI

Written for Gemini CLI: the file is GEMINI.md. Also seen: mentions AGENTS.md.

This is nantobv/pituitary's own configuration. It tells Gemini CLI how to work on pituitary itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pituitary configures →

not rated 22repo 3mo ago A scan 660 tokens copy · 92% MIT
View source ↗ nantobv/pituitary
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/GEMINI.md
Clone the repo
git clone --depth 1 https://github.com/nantobv/pituitary

Made for: Gemini CLI.

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.

agentmods badge for pituitary GEMINI.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nantobv/pituitary/gemini-md.svg)](https://agentmods.dev/instructions/nantobv/pituitary/gemini-md)
Your own site
<a href="https://agentmods.dev/instructions/nantobv/pituitary/gemini-md"><img src="https://agentmods.dev/badge/instructions/nantobv/pituitary/gemini-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 660 This file is loaded in full into every session.
When invoked 660 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 92% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00660 $0.00660
Opus 5 $0.00330 $0.00330
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

Measured 8d ago against content hash 9cdb4d48b6e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

pituitary GEMINI.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 8d 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

This is a copy

92% identical to pituitary CLAUDE.md — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

GEMINI.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 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. Gemini-specific refresh behavior belongs in tooling, not in a second policy file.

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 · 51 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.

  1. 8d ago First seen · 51 lines · 660 tokens per session scan A 9cdb4d48b6e8

Subscribe to this mod's changes

pituitary GEMINI.md is an instructions file published in the GitHub repository nantobv/pituitary (22 stars, last pushed 3mo ago), licensed MIT. It adds 660 tokens to every session, about $0.0033 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to pituitary CLAUDE.md, differing in 1 line, and is treated as a copy.

ai-toolsclideveloper-toolsdocumentationmcp
Related

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.

openai/codex · 5,182 tokens

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

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens