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/narumiruna/pi-extensions/agents-mdgit clone --depth 1 https://github.com/narumiruna/pi-extensionsWrote 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/narumiruna/pi-extensions/agents-md)<a href="https://agentmods.dev/instructions/narumiruna/pi-extensions/agents-md"><img src="https://agentmods.dev/badge/instructions/narumiruna/pi-extensions/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 | $0.03478 | $0.03478 |
| Opus 5 | $0.01739 | $0.01739 |
| Sonnet 5 | $0.00696 | $0.00696 |
| Haiku 4.5 | $0.00348 | $0.00348 |
Grade A, and why
pi-extensions 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 today.
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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Documentation and communication
- Lead with the most important relevant information, then add only necessary detail.
- Use clear, familiar words and concise, accurate sentences without repetition.
- Explain the main idea simply before adding technical detail.
- Make documented rules specific and verifiable.
- In human-facing documentation such as README files, use concise paragraphs for narrative text and lists only when separate items are easier to scan.
- Keep AGENTS.md instructions as bullet lists with one enforceable sentence per bullet.
Repository structure
- This Node.js and TypeScript monorepo contains Pi extension packages, project-local Pi extensions, and reusable libraries.
- Keep publishable extension packages and reusable libraries under
packages/<package>/. - Keep package implementation source under
packages/<package>/src/. - Keep small repository-only Pi extensions and their supporting implementation files under
.pi/extensions/<extension>/, withindex.tsas the entrypoint. - Each package owns its manifest, README, license, and TypeScript configuration.
- Do not classify extension packages with repository-specific lifecycle metadata; treat every active packaged extension uniformly.
- Treat
.pi/extensions/as a self-contained project-resource boundary unrelated to extension packages underpackages/. - Keep a project-local extension's implementation, helpers, documentation, and any requested tests inside its own
.pi/extensions/<extension>/directory. - Do not add or modify package manifests, workspaces, Changesets, package tests, root test support, or shared TypeScript configuration for a project-local extension unless the user explicitly asks.
- Project-local extensions do not require package manifests, Changesets, publication files, or packaged-extension verification gates.
- Promote a project-local extension into
packages/only when the user explicitly requests independent installation, reuse, versioning, or publication. - Keep deprecated reference packages under
deprecated/, which active checks exclude. - Root files such as
package.json,package-lock.json,biome.json,tsconfig.json, and.github/workflows/*own shared tooling. - Never edit
node_modules/. - When code mirrors, filters, or predicts external runtime behavior, inspect the installed implementation and enumerate all relevant decision branches and equivalence classes; do not infer behavior from types, raw values, or review examples.
- Keep published files aligned with each manifest's
fileslist andpi.extensionsentry.
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.
- today Changed · +2 lines · +113 tokens per session c4e8c6fd92c2
- yesterday Changed · +23 tokens per session fe69c8a8b10e
- 5d ago First seen · 178 lines · 3,342 tokens per session scan A e33ebf8f6ae7
pi-extensions AGENTS.md is an instructions file published in the GitHub repository narumiruna/pi-extensions (505 stars, last pushed today), licensed MIT. It adds 3,478 tokens to every session, about $0.0174 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
mikro-orm copilot-instructions.md
Copilot instructions for mikro-orm/mikro-orm, covering mikroorm typescript orm development instructions, working effectively, environment setup, building and testing and environment reset (when pulling master).
zapo AGENTS.md
AGENTS.md instructions for vinikjkkj/zapo, covering agents.md – development guide for zapo, 1. non-negotiable principles, source of truth: wa-web/ and wa-mob/, 2. current project layout and monorepo conventions.
Accordion CLAUDE.md
Instructions for a-Fig/Accordion, covering claude.md — accordion, key urls, terminology, codebase map and engine — single source of truth.
Accordion AGENTS.md
Instructions for a-Fig/Accordion, a project described as: 🏆 AI Hackathon 2026 @ UC Berkeley Intelligent context management for developers.
pi-extensions AGENTS.md
AGENTS.md instructions for MattDevy/pi-extensions, covering pi-extensions, repository structure, commands (run from repo root), working on a specific package and readme conventions.
pi-extensions CLAUDE.md
Claude Code instructions for MattDevy/pi-extensions, covering claude.md, commands, architecture, data flow and key modules.