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/notlate-cn/code-reader-skills/claude-mdgit clone --depth 1 https://github.com/notlate-cn/code-reader-skillsWrote 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/notlate-cn/code-reader-skills/claude-md)<a href="https://agentmods.dev/instructions/notlate-cn/code-reader-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/notlate-cn/code-reader-skills/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.01118 | $0.01118 |
| Opus 5 | $0.00559 | $0.00559 |
| Sonnet 5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
code-reader-skills 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 — 137 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.
Project Overview
This is a Claude Skills repository containing bilingual (Chinese/English) code analysis tools based on cognitive science research. The skills help developers achieve deep understanding of source code through elaborative interrogation, self-explanation testing, and retrieval practice.
Core Philosophy: Understanding WHY > Knowing WHAT
Repository Structure
deep-code-understanding-skill/
├── code-reader-zh/ # Chinese version skill
│ ├── SKILL.md # Source skill definition (primary)
│ └── code-reader-zh.skill # Packaged skill file
├── code-reader-en/ # English version skill
│ ├── SKILL.md # Source skill definition (primary)
│ └── code-reader-en.skill # Packaged skill file
├── README.md # Bilingual project documentation
├── LICENSE # MIT License
└── CLAUDE.md # This file
Key Architecture
Skill Definition Format
Skills use YAML frontmatter followed by Markdown content:
---
name: code-reader-v2-cn
description: [Trigger words and brief description]
---
# [Content follows...]
Three Analysis Modes
| Mode | Duration | Use Case | Key Features |
|---|---|---|---|
| Quick | 5-10 min | Code review, quick browse | Overview, dependencies, key segments |
| Standard | 15-20 min | Learning, research | WHY analysis, design patterns, algorithm deep dive |
| Deep | 30+ min | Mastery, interview prep | Application transfer, quality verification, progressive generation |
Core Analysis Framework
The skills implement a 9-step research-driven workflow:
- Quick Overview - Language, scale, dependencies, code type
- Elaborative Interrogation - 3 WHYs for background/motivation
- Concept Network Construction - Concept relationships with WHYs
- Algorithm & Theory Analysis - Complexity, rationale, references
- Design Pattern Recognition - WHY used, alternatives, implications
- Line-by-Line Analysis - Scenario-based comments with execution tracking
- Application Transfer Testing - At least 2 different scenarios
- Dependencies & Usage - WHY for each dependency
- Quality Verification - Self-assessment checklist
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 · 137 lines · 1,118 tokens per session scan A 165f75ed764f
code-reader-skills CLAUDE.md is an instructions file published in the GitHub repository notlate-cn/code-reader-skills (152 stars, last pushed 5mo ago), licensed MIT. It adds 1,118 tokens to every session, about $0.0056 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.