Borrowing it
Nothing to install: this file belongs to feniix/pi-extensions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/feniix/pi-extensions/main/AGENTS.mdgit clone --depth 1 https://github.com/feniix/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/feniix/pi-extensions/agents-md)<a href="https://agentmods.dev/instructions/feniix/pi-extensions/agents-md"><img src="https://agentmods.dev/badge/instructions/feniix/pi-extensions/agents-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.
<a href="https://agentmods.dev/instructions/feniix/pi-extensions/agents-md"><img src="https://agentmods.dev/badge/instructions/feniix/pi-extensions/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01660 | $0.01660 |
| Opus 5.5 | $0.00664 | $0.00664 |
| Sonnet 5.5 | $0.00332 | $0.00332 |
| Haiku 4.5 | $0.00166 | $0.00166 |
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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- This repo is a pnpm workspace with independent packages in
packages/*; use the exact rootpackageManagerpin. - Each package follows a consistent layout:
extensions/index.tsfor the pi extension entry point.__tests__/for Vitest tests (e.g.,index.test.ts,helpers.test.ts).README.md,package.json, andLICENSEper package.
- Root-level configs live in
biome.json,tsconfig.json, andvitest.config.ts. docs/solutions/contains documented solutions to past problems (bugs, best practices, workflow patterns), organized by category with YAML frontmatter fields such asmodule,tags, andproblem_type; relevant when implementing or debugging in documented areas.CONCEPTS.mddefines shared domain vocabulary (entities, named processes, status concepts) with project-specific meaning; relevant when orienting to the codebase or discussing domain concepts.
Build, Test, and Development Commands
Run these from the repo root unless noted:
pnpm install --frozen-lockfile— install the committed dependency graph.pnpm run lint— Biome lint/format checks.pnpm run lint:fix— auto-fixable Biome issues.pnpm run typecheck— TypeScript type checking only.pnpm run test— Vitest test suite.pnpm run test:coverage— Vitest coverage run with repo-wide thresholds.pnpm run check— lint + typecheck.pnpm run check:ci— CI-friendly Biome + typecheck.pnpm run ci:detect <base> <head>— show which packages the CI workflow will check for a given diff.pnpm run audit:workspaces— audit the shared lockfile, including root dependencies; preserve failures.- When changing dependencies, run
pnpm installand review the lock and version-scoped build approvals inpnpm-workspace.yaml. Tool execution fails on stale dependencies rather than silently reinstalling.
Local package testing:
cd packages/<package-name>pi -e .— run the package in pi without installing.- From the repo root:
pnpm exec biome ci packages/<package-name>— lint a single package. - From the repo root:
pnpm exec tsc --noEmit --project packages/<package-name>/tsconfig.json— typecheck a single package using the shared root TS config via the package wrapper tsconfig. - From the repo root:
pnpm exec vitest run packages/<package-name>/__tests__— run tests for a single package.
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.
- 2d ago Changed · -7 lines · -70 tokens per session 98ece15a905c
- 26d ago Changed · +3 lines · +144 tokens per session a3a20be42bf8
- 27d ago Changed · +7 lines · +70 tokens per session e16fc0b5a575
- 1mo ago First seen · 104 lines · 1,516 tokens per session scan A e54bda4a1869
pi-extensions AGENTS.md is an instructions file published in the GitHub repository feniix/pi-extensions (25 stars, last pushed 3d ago), licensed MIT. It adds 1,660 tokens to every session, about $0.0066 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.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.