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/jvm/pi-mono/agents-mdgit clone --depth 1 https://github.com/jvm/pi-monoWhat 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.01570 | $0.01570 |
| Opus 5 | $0.00785 | $0.00785 |
| Sonnet 5 | $0.00314 | $0.00314 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
pi-mono 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Scope and precedence
pi-mono contains independently published Pi packages under packages/*.
Source of truth, highest first:
- Executable config:
package.json, tests, CI, release workflows. - Root
AGENTS.md: monorepo invariants. - Package
AGENTS.md: package-only invariants and exceptions. - README: user-facing product, setup, and usage.
- CHANGELOG: released behavior.
Package instructions must not repeat root policy. If guidance conflicts with executable config, fix the stale guidance in the same change.
Required workflow
- Read affected package
AGENTS.mdand inspect worktree/branch. - Map impact across package-local, cross-package, and root artifacts before editing.
- Keep changes scoped; update tests with behavior.
- Update user docs only when triggers below apply.
- Run validation from the matrix.
- Inspect
git diff --check,git diff --stat, and packed files when publishing changes.
Impact scan includes root README/index, AGENTS.md, root manifest/lockfile, shared scripts/templates, workflows, release metadata, and security policy. Update only artifacts affected by the change; keep package listings, versions, commands, and policy synchronized.
Bug fixes require regression coverage of the broken integration path. Helper-only tests are insufficient when removing feature wiring would still pass. Private Pi API patches require render/contract tests and a documented smoke test when automation cannot cover runtime behavior.
Package contract
New packages should copy canonical config files from templates/package/, then add only needed resources (extensions/, skills/, prompts/, themes/). Every package requires:
package.json,tsconfig.json,.editorconfig,.gitignoreAGENTS.md,README.md,CHANGELOG.mdCODE_OF_CONDUCT.md,CONTRIBUTING.md,LICENSE,SECURITY.md
Do not create CLAUDE.md; only Claude Code owns that file. Do not publish tests, plans, agent files, generated builds, secrets, settings, or machine paths.
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 · 149 lines · 1,570 tokens per session scan A 53ab45a82809
pi-mono AGENTS.md is an instructions file published in the GitHub repository jvm/pi-mono (21 stars, last pushed 10d ago), licensed MIT. It adds 1,570 tokens to every session, about $0.0078 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
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.