Borrowing it
Nothing to install: this file belongs to 2ykwang/cview. 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/2ykwang/cview/main/AGENTS.mdgit clone --depth 1 https://github.com/2ykwang/cviewWrote 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/2ykwang/cview/agents-md)<a href="https://agentmods.dev/instructions/2ykwang/cview/agents-md"><img src="https://agentmods.dev/badge/instructions/2ykwang/cview/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/2ykwang/cview/agents-md"><img src="https://agentmods.dev/badge/instructions/2ykwang/cview/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.00652 | $0.00652 |
| Opus 5.5 | $0.00261 | $0.00261 |
| Sonnet 5.5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
cview 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Repository instructions for coding agents. README.md is the human-facing
product and contributor guide; keep agent-specific guidance here.
Bootstrap and verification
Use the Node version in .node-version. In a fresh checkout, install the
locked dependencies and Chromium once:
npm run bootstrap
Use the smallest relevant test while iterating, then run the appropriate gate:
npm test -- path/to/file.test.ts # focused Vitest run
npm run check # types, lint, design lint, Vitest, build
npm run check:all # check plus production Playwright flows
Run npm run check before handing off any source or configuration change. Run
npm run check:all when a change can cross the server/browser boundary or
affect navigation, themes, rendering, export, capture, or build configuration.
For DESIGN.md-only work, npm run lint:design is the focused gate.
Where behavior belongs
src/server.tscomposes the app; filesystem, search, security, and HTTP/SSE behavior belongs in focused modules undersrc/server/.src/shared/contracts.tsparses and normalizes JSONL records and API responses.- Frontend transport belongs in
api/, pure conversation behavior indomain/, browser lifecycles inhooks/, and screen/display work inpages/andcomponents/. - Live and standalone export behavior belongs in
src/frontend/src/export/. - For UI or export presentation changes, read
DESIGN.md. Semantic colors live instyles/theme.css, shared conversation rules instyles/conversation.css, and typed React references instyles/tokens.ts.
Contracts to preserve
- Parse Claude records through the shared contracts and keep unknown record kinds visible instead of silently discarding them.
- Keep
~/.clauderead-only and write derived indexes to the external cache. Never copy real session files into tests; use small JSONL files with invented data. - Bind to loopback, reject non-local API clients/origins, and validate every project, session, and agent path segment before filesystem access.
- Keep cold filesystem scans bounded; do not fan out unbounded reads across all sessions.
- Preserve public CLI names, environment variables, API behavior, stored-data compatibility, message ordering, and stable message IDs unless requested.
- Standalone HTML must remain offline-capable. Re-export must not nest controls or create multiple toolbars, and capture must work in both themes.
- Keep heavy export/capture dependencies behind the existing lazy boundary.
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 First seen · 65 lines · 652 tokens per session scan A 032ee1f136e0
cview AGENTS.md is an instructions file published in the GitHub repository 2ykwang/cview (20 stars, last pushed 2mo ago), licensed MIT. It adds 652 tokens to every session, about $0.0026 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.