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/peonping/openpeon/claude-mdgit clone --depth 1 https://github.com/PeonPing/openpeonWrote 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/peonping/openpeon/claude-md)<a href="https://agentmods.dev/instructions/peonping/openpeon/claude-md"><img src="https://agentmods.dev/badge/instructions/peonping/openpeon/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 | $0.00648 | $0.00648 |
| Opus 5 | $0.00324 | $0.00324 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
openpeon 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 4d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenPeon
OpenPeon is an open standard (CESP v1.0) for coding event sounds. Any agentic IDE or terminal editor can implement CESP to give developers audio feedback when tasks complete, errors occur, or input is needed.
Key Directories
spec/-- CESP v1.0 specification, JSON schemas (openpeon.schema.jsonfor pack manifests,registry-entry.schema.jsonfor registry entries)examples/-- Example sound packs (peon, glados) that validate against the schemassite/-- Next.js site deployed to openpeon.com via Vercelscripts/-- Cross-repo utility scripts (update-pack-counts.shfor syncing pack counts)docs/-- Architecture documents (registry-design.md,download-tracking-plan.md,plans/)tests/-- Schema validation tests
Build Commands
Site (from site/ directory)
npm run dev-- Start dev servernpm run build-- Production buildnpm run lint-- ESLint
Tests (from repo root)
npm test-- Run all tests (schema validation)npm run test:schema-- Run schema validation tests only
Architecture Notes
- Pack data is fetched at request time with ISR, not at build time.
site/src/lib/registry.tsfetches the registry index frompeonping.github.io/registry/index.json, then each pack'sopenpeon.jsonmanifest from GitHub raw URLs, with bounded concurrency and retries. Fetches are cached withrevalidate: 86400(24h) underREGISTRY_TAG. - A malformed community manifest is dropped with a
[registry] dropping pack ...console warning rather than failing the render. If the live site shows far fewer packs than the registry, check the deploy logs for these warnings. site/src/app/api/revalidate/route.tsaccepts a POST with anx-revalidate-secretheader and busts the registry cache tag. It only works onceREVALIDATE_SECRETis set in the Vercel project env; until then a freshvercel --proddeploy is the way to reset the ISR cache.- Audio files are served directly from GitHub raw URLs (no local copies).
- The site is deployed to Vercel; the Vercel project's root directory is
site/, so runvercelfrom the REPO ROOT, not fromsite/. - Schemas use JSON Schema Draft 7.
- CI (
.github/workflows/ci.yml) runs root schema tests plus site lint and build on every push/PR to main.
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.
- 4d ago First seen · 40 lines · 648 tokens per session scan A 4f01ff3891c7
openpeon CLAUDE.md is an instructions file published in the GitHub repository PeonPing/openpeon (103 stars, last pushed 24d ago), licensed MIT. It adds 648 tokens to every session, about $0.0032 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.