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/gvkhosla/compound-engineering-pi/claude-mdgit clone --depth 1 https://github.com/gvkhosla/compound-engineering-piWrote 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/gvkhosla/compound-engineering-pi/claude-md)<a href="https://agentmods.dev/instructions/gvkhosla/compound-engineering-pi/claude-md"><img src="https://agentmods.dev/badge/instructions/gvkhosla/compound-engineering-pi/claude-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.1 | $0.02735 | $0.02735 |
| Opus 5 | $0.01367 | $0.01367 |
| Sonnet 5 | $0.00547 | $0.00547 |
| Haiku 4.5 | $0.00274 | $0.00274 |
Grade A, and why
compound-engineering-pi 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- compound-engineering-plugin CLAUDE.md — 92% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Every Marketplace - Claude Code Plugin Marketplace
This repository is a Claude Code plugin marketplace that distributes the compound-engineering plugin to developers building with AI-powered tools.
Repository Structure
every-marketplace/
├── .claude-plugin/
│ └── marketplace.json # Marketplace catalog (lists available plugins)
├── docs/ # Documentation site (GitHub Pages)
│ ├── index.html # Landing page
│ ├── css/ # Stylesheets
│ ├── js/ # JavaScript
│ └── pages/ # Reference pages
└── plugins/
└── compound-engineering/ # The actual plugin
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
├── agents/ # 24 specialized AI agents
├── commands/ # 13 slash commands
├── skills/ # 11 skills
├── mcp-servers/ # 2 MCP servers (playwright, context7)
├── README.md # Plugin documentation
└── CHANGELOG.md # Version history
Philosophy: Compounding Engineering
Each unit of engineering work should make subsequent units of work easier—not harder.
When working on this repository, follow the compounding engineering process:
- Plan → Understand the change needed and its impact
- Delegate → Use AI tools to help with implementation
- Assess → Verify changes work as expected
- Codify → Update this CLAUDE.md with learnings
Working with This Repository
Adding a New Plugin
- Create plugin directory:
plugins/new-plugin-name/ - Add plugin structure:
plugins/new-plugin-name/ ├── .claude-plugin/plugin.json ├── agents/ ├── commands/ └── README.md - Update
.claude-plugin/marketplace.jsonto include the new plugin - Test locally before committing
Updating the Compounding Engineering Plugin
When agents, commands, or skills are added/removed, follow this checklist:
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.
- 5d ago First seen · 381 lines · 2,735 tokens per session scan A a203d3be8c2c
compound-engineering-pi CLAUDE.md is an instructions file published in the GitHub repository gvkhosla/compound-engineering-pi (51 stars, last pushed 4mo ago), licensed MIT. It adds 2,735 tokens to every session, about $0.0137 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
pi-fabric AGENTS.md
AGENTS.md instructions for monotykamary/pi-fabric, covering agents.md, golden rule: build when done, before committing, incremental checks while iterating and package manager.
LaPis AGENTS.md
AGENTS.md instructions for GeneGulanesJr/LaPis, covering protocols, 1. code & doc retrieval — use memory-code / memory-doc, 2. persistent memory — automatic, when to use the tools and content format.
my-pi AGENTS.md
AGENTS.md instructions for spences10/my-pi, covering agents.md, orientation, repository-specific skills, source of truth order and commit and changeset ownership.
TelePi AGENTS.md
Instructions for benedict2310/TelePi, covering repository guidelines, project structure & module organization, build, test, and development commands, operational commands and coding style & naming conventions.
pi-ask AGENTS.md
Instructions for eko24ive/pi-ask, covering agents.md, project scope, project goals, tech stack and commands.
pi-server AGENTS.md
Instructions for tryingET/pi-server, covering agents.md — crystallized learnings for pi-server, canonical references, architecture principles, adr-0001: atomic outcome storage and the invariant.