Borrowing it
Nothing to install: this file belongs to PeakCode-AI/PeakCode. 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/PeakCode-AI/PeakCode/main/CLAUDE.mdgit clone --depth 1 https://github.com/PeakCode-AI/PeakCodeWrote 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/peakcode-ai/peakcode/claude-md)<a href="https://agentmods.dev/instructions/peakcode-ai/peakcode/claude-md"><img src="https://agentmods.dev/badge/instructions/peakcode-ai/peakcode/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/peakcode-ai/peakcode/claude-md"><img src="https://agentmods.dev/badge/instructions/peakcode-ai/peakcode/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.02528 | $0.02528 |
| Opus 5.5 | $0.01011 | $0.01011 |
| Sonnet 5.5 | $0.00506 | $0.00506 |
| Haiku 4.5 | $0.00253 | $0.00253 |
Grade A, and why
PeakCode 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- KodoCode AGENTS.md — 88% identical, 179 lines differ
- okcode AGENTS.md — 81% identical, 180 lines differ
How it starts
The opening of the file, as written. The whole thing — 199 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.
Task Completion Requirements
- All of
bun fmt,bun lint, andbun typecheckmust pass before considering tasks completed. - Treat
bun fmt,bun lint, andbun typecheckas heavyweight workspace checks: bundle them into one final verification pass per task whenever possible, and avoid rerunning the full set repeatedly during iteration. - If a user asks for a small follow-up right after a recent full verification pass, prefer no rerun or the smallest reasonable re-check unless the user explicitly asks for full validation again.
- NEVER run
bun test. Always usebun run test(runs Vitest).
Commands
# Development
bun run dev # full dev mode (server + web, via scripts/dev-runner.ts)
bun run dev:server # server only
bun run dev:web # web only
bun run dev:desktop # desktop (Electron) dev mode
bun run electron:dev # Electron with isolated home dir
# Build
bun run build # full monorepo build (turbo)
bun run build:contracts # build contracts only (other packages depend on it)
# Test — always use bun run test, never bun test
bun run test # full test suite (turbo)
bunx --bun vitest run path/to/file # run a single test file
bunx --bun vitest run -t "pattern" # run tests matching a pattern
# Lint & Format
bun fmt # oxfmt
bun fmt:check # oxfmt --check (CI)
bun lint # oxlint
bun typecheck # full monorepo typecheck (turbo)
# Desktop distribution
bun run dist:desktop:dmg # macOS .dmg
bun run dist:desktop:linux # Linux AppImage
bun run dist:desktop:win # Windows NSIS installer
# Clean
bun run clean # remove all node_modules, dist, .turbo
Monorepo Architecture
Peak Code is a Bun monorepo (packageManager: [email protected]) using Turborepo and Effect-TS throughout. The catalog system in package.json pins all Effect packages to the same snapshot (from pkg.pr.new) to avoid version skew. The linker is isolated (bunfig.toml), meaning each package has its own node_modules.
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 · -1 tokens per session a266af614514
- 1mo ago Changed · +143 lines · +1,838 tokens per session 155515113987
- 2mo ago First seen · 56 lines · 691 tokens per session scan A c1b9ca2a54f3
PeakCode CLAUDE.md is an instructions file published in the GitHub repository PeakCode-AI/PeakCode (142 stars, last pushed 1mo ago), licensed MIT. It adds 2,528 tokens to every session, about $0.0101 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.