Borrowing it
Nothing to install: this file belongs to maike009/context-engineering-intro-CN. 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/maike009/context-engineering-intro-CN/main/CLAUDE.mdgit clone --depth 1 https://github.com/maike009/context-engineering-intro-CNWrote 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/maike009/context-engineering-intro-cn/claude-md)<a href="https://agentmods.dev/instructions/maike009/context-engineering-intro-cn/claude-md"><img src="https://agentmods.dev/badge/instructions/maike009/context-engineering-intro-cn/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/maike009/context-engineering-intro-cn/claude-md"><img src="https://agentmods.dev/badge/instructions/maike009/context-engineering-intro-cn/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.00693 | $0.00693 |
| Opus 5.5 | $0.00277 | $0.00277 |
| Sonnet 5.5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
context-engineering-intro-CN 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.
This is a copy
100% identical to context-engineering-intro CLAUDE.md β 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing β 59 lines β stays where its author put it; the contents beside it link to each section on GitHub.
π Project Awareness & Context
- Always read
PLANNING.mdat the start of a new conversation to understand the project's architecture, goals, style, and constraints. - Check
TASK.mdbefore starting a new task. If the task isnβt listed, add it with a brief description and today's date. - Use consistent naming conventions, file structure, and architecture patterns as described in
PLANNING.md. - Use venv_linux (the virtual environment) whenever executing Python commands, including for unit tests.
π§± Code Structure & Modularity
- Never create a file longer than 500 lines of code. If a file approaches this limit, refactor by splitting it into modules or helper files.
- Organize code into clearly separated modules, grouped by feature or responsibility.
For agents this looks like:
agent.py- Main agent definition and execution logictools.py- Tool functions used by the agentprompts.py- System prompts
- Use clear, consistent imports (prefer relative imports within packages).
- Use clear, consistent imports (prefer relative imports within packages).
- Use python_dotenv and load_env() for environment variables.
π§ͺ Testing & Reliability
- Always create Pytest unit tests for new features (functions, classes, routes, etc).
- After updating any logic, check whether existing unit tests need to be updated. If so, do it.
- Tests should live in a
/testsfolder mirroring the main app structure.- Include at least:
- 1 test for expected use
- 1 edge case
- 1 failure case
- Include at least:
β Task Completion
- Mark completed tasks in
TASK.mdimmediately after finishing them. - Add new sub-tasks or TODOs discovered during development to
TASK.mdunder a βDiscovered During Workβ section.
π Style & Conventions
- Use Python as the primary language.
- Follow PEP8, use type hints, and format with
black. - Use
pydanticfor data validation. - Use
FastAPIfor APIs andSQLAlchemyorSQLModelfor ORM if applicable. - Write docstrings for every function using the Google style:
def example(): """ Brief summary. Args: param1 (type): Description. Returns: type: Description. """
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 Β· 59 lines Β· 693 tokens per session scan A 7e355492496c
context-engineering-intro-CN CLAUDE.md is an instructions file published in the GitHub repository maike009/context-engineering-intro-CN (2 stars, last pushed 1y ago), licensed MIT. It adds 693 tokens to every session, about $0.0028 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to context-engineering-intro CLAUDE.md, differing in 0 lines, and is treated as a copy.
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.