Borrowing it
Nothing to install: this file belongs to ProgrammerAnthony/Expert-Coding-Harness. 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/ProgrammerAnthony/Expert-Coding-Harness/master/.cursor/skills/llm-wiki-interview/SKILL.mdgit clone --depth 1 https://github.com/ProgrammerAnthony/Expert-Coding-HarnessWrote 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/programmeranthony/expert-coding-harness/llm-wiki-interview)<a href="https://agentmods.dev/skills/programmeranthony/expert-coding-harness/llm-wiki-interview"><img src="https://agentmods.dev/badge/skills/programmeranthony/expert-coding-harness/llm-wiki-interview/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/programmeranthony/expert-coding-harness/llm-wiki-interview"><img src="https://agentmods.dev/badge/skills/programmeranthony/expert-coding-harness/llm-wiki-interview.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.00126 | $0.00788 |
| Opus 5.5 | $0.00050 | $0.00315 |
| Sonnet 5.5 | $0.00025 | $0.00158 |
| Haiku 4.5 | $0.00013 | $0.00079 |
Grade A, and why
llm-wiki-interview 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 2mo 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
LLM Wiki Interview（合并技能）
铁律：raw/ 与 wiki/ 分工不同——写资料只按 Raw 层规范；把资料编译成可查询 Wiki 只按 Wiki 层规范，且 ingest 时不得改 raw/。
与两层文件的关系
| 阶段 | 目录与职责 | 完整规范 |
|---|---|---|
| Raw 层 | 只写 raw/：唯一检索总账 _research.md、basic/、blog/、assets/；不写 wiki/ |
references/raw-layer.md |
| Wiki 层 | 只读 raw/，读写 wiki/：实体/概念/摘要页、wiki/index.md、wiki/log.md、图片同步到 wiki/assets/ |
references/wiki-layer.md |
衔接：两层只通过同一份 raw/ 对齐——先（或并行由用户维护）在 raw/ 里按 Raw 层落料，再在用户要求「导入 / ingest / 编译 wiki」时按 Wiki 层把内容编译进 wiki/。
何时加载哪一份 reference
- 用户要做 关键词拆分、检索笔记、basic 长文、blog 编译、用户供稿、每轮 blog≤5 等：先读
references/raw-layer.md，并遵守其中自检清单。 - 用户要说 创建知识库、从 raw 导入 wiki、查询 wiki、lint、维护 index/log：先读
references/wiki-layer.md。 - 同一会话里先 raw 后 wiki：两段规范都可能在一次任务里用到；切换阶段时明确当前手是否允许写
raw/还是仅写wiki/。
核心理念（与 Wiki 层一致）
用 LLM 持续维护结构化 Markdown 知识库（wiki/），而不是每次提问只做一次性检索；raw/ 作为不可变来源层与面试向加工层（basic + blog），再经 ingest 进入 wiki/。更细的哲学与操作见 references/wiki-layer.md 开头与「三大操作」。
参考资源（必读顺序）
references/raw-layer.md— Raw 层全部规则与质量自检。references/wiki-layer.md— Wiki 层 ingest / query / lint、初始化目录、实战经验（含raw/blog全文块与「核心内容提取」何者为真）。
项目内说明与出处见同目录 README.md。
What ships with it
3 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.
- 2mo ago First seen · 36 lines · 126 tokens per session scan A a4631c558a38
llm-wiki-interview is a skill published in the GitHub repository ProgrammerAnthony/Expert-Coding-Harness (246 stars, last pushed 5mo ago), licensed MIT. It adds 126 tokens to every session and 788 once invoked, about $0.0005 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 skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.