Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/lihaozheCharlie/TwhWikinpx agentmods add skills/lihaozhecharlie/twhwiki/skill-systemWrote 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/lihaozhecharlie/twhwiki/skill-system)<a href="https://agentmods.dev/skills/lihaozhecharlie/twhwiki/skill-system"><img src="https://agentmods.dev/badge/skills/lihaozhecharlie/twhwiki/skill-system/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/lihaozhecharlie/twhwiki/skill-system"><img src="https://agentmods.dev/badge/skills/lihaozhecharlie/twhwiki/skill-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00797 |
| Opus 5 | $0.00023 | $0.00398 |
| Sonnet 5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
common-skill-system 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 11d 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.
What it actually says
通用：Skill 体系
用于创建、重构、验证或调试本 wiki 的 Skill 体系。
分析和验证保持只读。只有用户明确要求修改时才变更体系。
设计原则
- 单一入口：根
AGENTS.md是唯一运行入口和路由来源，skills/是唯一 Skill 内容源。 - 每个
SKILL.md保持聚焦。较长的模式专用配方放入references/，只读取当前选中的参考文件。 - 确定性工作放进工具，需要判断的工作放进 Skill。
- 根
AGENTS.md保持可直接执行：先区分读写模式，再把请求路由到准确的规范 Skill。 - 每个 wiki 类别只设一个负责 Skill。其他 Skill 路由给负责人，不复制其模板。
- 共享质量规则只放在
skills/common/quality-gate/SKILL.md。 - 只读请求绝不授权修复、摄取、追加日志或重新生成索引。
必需文件
AGENTS.md：唯一入口、授权边界和分发映射。skills/common/skill-system/module-map.md：构建、通用、消费模块的职责和保留映射。skills/build/*/SKILL.md：构建模块入口。skills/common/*/SKILL.md：共享质量和 Skill 体系规则。skills/consume/*/SKILL.md：查询与消费流程。skills/common/skill-system/trigger-cases.json：供回归审阅的正向和负向路由规格。tools/validate_skill_system.py：确定性的结构和安全检查。
trigger-cases.json 是静态路由规格。验证器检查覆盖、冲突和引用，不会调用模型，因此不能把它的通过等同于真实的自动触发评测；高风险路由变化仍需独立行为评测。
更新要求
修改 Skill 体系时：
- 更新根
AGENTS.md中的唯一路由表。 - 映射变化时更新
skills/common/skill-system/module-map.md。 - 人与模型的工作流变化时，更新
AGENTS.md、wiki/AGENTS.md和wiki/99 维护规则/维护手册 v2.md。 - 通过引用或迁移详细配方，保留旧模板中有价值的内容。
- 追加
wiki/log.md。 - 运行质量门。
体系检查清单
- 每个 Skill 是否都有清晰的前置元数据
name和description？ - 每个规范 Skill 是否都由根
AGENTS.md的唯一路由表覆盖？ - 每个 Skill 是否说明了使用时机、先读内容以及所需输出或验证？
- 分析触发与修改触发是否明确分离？
- 每个 wiki 类别是否恰好只有一个模板负责人？
- 影响矩阵是否覆盖所有构建层？
- 脆弱的确定性步骤是否被表示为命令或工具？
- 审计工具是否默认使用只读或检查模式？
- 在能防止重复错误的地方，是否记录了失败模式和反模式？
验证
python3 tools/validate_skill_system.py
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 62 lines · 47 tokens per session scan A 21e258a4fda6
common-skill-system is a skill published in the GitHub repository lihaozheCharlie/TwhWiki (24 stars, last pushed 5d ago), licensed MIT. It adds 47 tokens to every session and 797 once invoked, about $0.0002 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 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…