What is Peek CLAUDE.md?

A set of instructions for the Peek project that requires design documents to be checked and updated before behavior, structure, or interaction changes are coded.

Reviewing existing design records, resolving conflicts with requested changes, recording the decision, and then implementing the agreed design.

It prevents the code from drifting away from the project’s documented decisions and makes disagreements visible before implementation starts.

How Gyangu/Peek configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Gyangu/Peek. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Gyangu/Peek/master/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/Gyangu/Peek

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/gyangu/peek/claude-md/github.svg)](https://agentmods.dev/instructions/gyangu/peek/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/gyangu/peek/claude-md"><img src="https://agentmods.dev/badge/instructions/gyangu/peek/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/gyangu/peek/claude-md"><img src="https://agentmods.dev/badge/instructions/gyangu/peek/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 876 This file is loaded in full into every session.

When invoked 876 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00876	$0.00876
Opus 5.5	$0.00350	$0.00350
Sonnet 5.5	$0.00175	$0.00175
Haiku 4.5	$0.00088	$0.00088

Measured 1mo ago against content hash c2467bfe56c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Peek 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.

CLAUDE.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Peek — working conventions

Every change goes through the documents

Any change that touches behaviour, structure or interaction goes through the documents before it goes into the code. The documents stay in the repository and are committed alongside the code, as the decision record for that change.

Since 2026-09-11 the documents are produced by Spec Kit (docs/design/2026-09-11-spec-kit-adoption.md). The order is fixed:

/speckit-specify — describe the change. This writes specs/NNN-short-name/spec.md: user scenarios, requirements, success criteria, and what the change explicitly does not do. Run /speckit-clarify when the description leaves questions open.
/speckit-plan — the technical plan, specs/NNN-short-name/plan.md. Its Constitution Check measures the plan against .specify/memory/constitution.md, which lists the decisions already made (and cites docs/PLAN.md for the details).
A conflict is settled first — if the check finds that what is being asked contradicts a standing decision, list the conflict explicitly for the user: what the documents decided, what is being asked now, and where the two fail to line up. Stop and wait for the user to say which side wins. Do not pick one and carry on. Spec Kit has no step for this; it is a rule.
/speckit-tasks — tasks.md, when the implementation is more than one sitting. For a small change the plan's Verification section is the task list. /speckit-analyze checks spec, plan and tasks against each other.
/speckit-implement — the code follows the documents. If the design turns out not to work during implementation, go back to step 3 and settle it again; do not let the code and the documents quietly diverge.

Documents:

Location: specs/NNN-short-name/ — one directory per change, numbered in sequence by /speckit-specify.
Language: English. Documents in this repository are written in English. The reason is that the repository is open source and the source comments were always English — 224 comments point at docs/design/, and the documents have to follow so that readers do not hit a language wall between a citation and its target (docs/design/2026-08-29-the-documentation-goes-english.md). pnpm test enforces it. Conversation with the user stays in Chinese; this rule governs only what is written into the repository.
plan.md carries two sections beyond the stock Spec Kit template, added by .specify/templates/overrides/plan-template.md:
1. Trade-offs — the other approaches considered, and why they lost
2. Verification — how to confirm the change is right (manual steps or tests)

Read the full file on GitHub · 63 lines

Changes

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 · +6 lines · +175 tokens per session c2467bfe56c6
2mo ago First seen · 57 lines · 701 tokens per session scan A 07e9387cb48a

Subscribe to this mod's changes

Peek CLAUDE.md is an instructions file published in the GitHub repository Gyangu/Peek (0 stars, last pushed 1mo ago), licensed MIT. It adds 876 tokens to every session, about $0.0035 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.

Planning

Peek CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Peek CLAUDE.mdGyangu/Peek	Instructions file	0	1mo ago	MIT	A	876	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

Peek: Instructions file for Claude Code