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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/peakcode-ai/peakcode/agents-md"><img src="https://agentmods.dev/badge/instructions/peakcode-ai/peakcode/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/peakcode-ai/peakcode/agents-md"><img src="https://agentmods.dev/badge/instructions/peakcode-ai/peakcode/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.01975 | $0.01975 |
| Opus 5.5 | $0.00790 | $0.00790 |
| Sonnet 5.5 | $0.00395 | $0.00395 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
PeakCode 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 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Task Completion Requirements
- Do not run
bun fmt,bun lint, orbun typecheckunless the user explicitly asks for them in the current conversation. - 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.
- If the user asks to focus on code only, do not run
bun fmt,bun lint, orbun typecheckautomatically. In that mode, make the code changes first and only run verification if the user explicitly asks for it. - NEVER run
bun test. Always usebun run test(runs Vitest).
PR Review
Before reviewing or merging any pull request, run the project's PR review script first:
bash scripts/pr-review.sh [PR_NUMBER] # review a specific PR
bash scripts/pr-review.sh # auto-detect PR from current branch
bash scripts/pr-review.sh --all # review all open PRs
The script checks a PR against CONTRIBUTING.md and AGENTS.md conventions across 16 categories: description completeness, diff size (<200 lines preferred), mergeability, changed-file hygiene, bun.lock drift, debug artifacts, bun fmt:check, bun typecheck, bun lint, affected tests, checklist compliance, scope purity, and AGENTS.md compliance.
Exit codes: 0 = approved (possibly with caveats), 1 = changes requested (errors must be fixed), 2 = rejected (do not merge).
Use the script's output to guide review comments and merge decisions. Do not merge a PR that returns exit code 1 or 2 without resolving the reported issues.
Project Snapshot
Peak Code is a minimal web GUI for using coding agents like Codex and Claude.
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 · +17 lines · +482 tokens per session 7e4cd85063da
- 2mo ago First seen · 91 lines · 1,493 tokens per session scan A a3283ad8d0d1
PeakCode AGENTS.md is an instructions file published in the GitHub repository PeakCode-AI/PeakCode (142 stars, last pushed 1mo ago), licensed MIT. It adds 1,975 tokens to every session, about $0.0079 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.