Borrowing it
Nothing to install: this file belongs to piperbox/piper. 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/piperbox/piper/main/CLAUDE.mdgit clone --depth 1 https://github.com/piperbox/piperWrote 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/piperbox/piper/claude-md)<a href="https://agentmods.dev/instructions/piperbox/piper/claude-md"><img src="https://agentmods.dev/badge/instructions/piperbox/piper/claude-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/piperbox/piper/claude-md"><img src="https://agentmods.dev/badge/instructions/piperbox/piper/claude-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.02745 | $0.02745 |
| Opus 5.5 | $0.01098 | $0.01098 |
| Sonnet 5.5 | $0.00549 | $0.00549 |
| Haiku 4.5 | $0.00275 | $0.00275 |
Grade A, and why
piper 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 1mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
An open-source, developer-first PaaS that gives you git push → live HTTPS URL on hardware you own — including a Raspberry Pi behind CGNAT. A single Go module produces multiple binaries:
piperd— the agent that runs on your box (control-plane, deployer, tunnel-client).piper-relay— the optional self-hostable cloud relay (SNI passthrough + tunnel server).piper-edge— the L4 entrypoint in front of N relays: routes each connection to the relay that owns the agent's tunnel (container-only, like the relay).piper— the CLI, a thin HTTP client topiperd.
Full design rationale lives in docs/superpowers/specs/ — read it before non-trivial work. Implementation plans live in docs/superpowers/plans/; work is delivered plan-by-plan, task-by-task, TDD-style. Plan 1 of 3 is the agent core, LAN-only (build a Dockerfile → run a container → health-check → serve at http://<app>.piper.localhost via managed Caddy, SQLite state). Plan 2 = relay + outbound tunnel + DNS-01 TLS. Plan 3 = GitHub webhook + PR-preview URLs. User-facing docs are organized by audience under docs/; read that map before adding or moving a doc.
Coding Principles
1. Think Before Coding
Don't assume. Don't hide confusion. Surface tradeoffs.
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
2. Simplicity First
Minimum code that solves the problem. Nothing speculative.
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
- Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
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.
- 1mo ago Changed · +27 tokens per session 4f196facfc0f
- 1mo ago Changed · +1 lines · +34 tokens per session 3341df04c4a3
- 2mo ago First seen · 158 lines · 2,684 tokens per session scan A 05115a3d68ee
piper CLAUDE.md is an instructions file published in the GitHub repository piperbox/piper (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,745 tokens to every session, about $0.0110 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-31.
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.