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 skills add phanghonghao/THU-Awesome-Skills --skill repo-docs-zhgit clone --depth 1 https://github.com/phanghonghao/THU-Awesome-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/skills/phanghonghao/thu-awesome-skills/repo-docs-zh)<a href="https://agentmods.dev/skills/phanghonghao/thu-awesome-skills/repo-docs-zh"><img src="https://agentmods.dev/badge/skills/phanghonghao/thu-awesome-skills/repo-docs-zh/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/skills/phanghonghao/thu-awesome-skills/repo-docs-zh"><img src="https://agentmods.dev/badge/skills/phanghonghao/thu-awesome-skills/repo-docs-zh.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.00062 | $0.01215 |
| Opus 5 | $0.00031 | $0.00607 |
| Sonnet 5 | $0.00012 | $0.00243 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
repo-docs-zh 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 12d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo-Docs ZH
Position
This is the Chinese-language overlay for repo-docs. Structure, page ownership, evidence rules, sync behavior, and validation come from ../repo-docs/SKILL.md. This overlay only changes language and Chinese reader experience.
Before acting, read:
../repo-docs/SKILL.md../repo-docs/REFERENCE.mdas the topic router only when detailed rules are needed- The routed topic file only when needed
../repo-docs/EXAMPLES.mdonly for output shape or tone examples needed by the task
Core Principle
Chinese repo-docs are not English docs translated line by line. They should rebuild the reader's conceptual handles in Chinese.
Chinese carries understanding: what this thing is, why it exists, what happens, and how to check it. English identifiers carry lookup: paths, commands, fields, API names, class/function names, metric names, package names, and dataset names.
Language Rules
- Use Chinese for titles, explanations, reading paths, examples, caveats, and change-log entries.
- Keep source identifiers exact. Do not translate paths, commands, keys, API names, class/function names, metric names, error strings, package names, or dataset names.
- First introduce repeated project terms as
中文名（English term）or中文名（source identifier）; later prefer the Chinese name. - README route sections use
## 阅读路径, not## Reader Routes. - Glossary columns are exactly
术语 | 项目里的意思 | 延伸阅读. - Narrative page evidence note:
证据状态：除特别标注外，本页基于当前源码已确认。
Chinese Handles And Source Locators
Use a Chinese reader handle before a source locator.
| Type | Use in Chinese docs |
|---|---|
| 读者句柄 | The narrative subject, such as “导入流程”, “会话层”, “结果汇总”, “运行脚本”. |
| 源码定位符 | Paths, functions, classes, fields, commands, artifact paths. Link directly with a Chinese label when one locator supports one claim. |
| 精确查表名 | Metrics, schema keys, tool parameters, artifact file names. Usually belongs in references/. |
| 外部术语 | Terms like benchmark, agent, workspace, protocol, memory. First mention gets a Chinese handle; later prefer Chinese when the term appears in the inspected repo. |
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.
- 12d ago First seen · 97 lines · 62 tokens per session scan A d04b69e9d614
repo-docs-zh is a skill published in the GitHub repository phanghonghao/THU-Awesome-Skills (8 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,215 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…