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 skills/szoloth/skill-pack/masternpx skills add SZoloth/skill-pack --skill mastergit clone --depth 1 https://github.com/SZoloth/skill-packWhat 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.00050 | $0.04251 |
| Opus 5 | $0.00025 | $0.02125 |
| Sonnet 5 | $0.00010 | $0.00850 |
| Haiku 4.5 | $0.00005 | $0.00425 |
Grade A, and why
master 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 3d 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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/master — Learning Mastery System
Turns passive reference documents into active expertise. Based on Justin Skycak's learning science (retrieval practice, spaced repetition, cognitive weightlifting) and Cedric Chin's expertise acceleration (case libraries, pattern recognition, cognitive flexibility theory).
Core principle: Reading a framework is not knowing it. You know it when you can recall it cold, bind it to real cases from your career, and deploy it under simulated pressure.
The learning sequence: Learn -> Quiz -> Cases -> Sim. Each mode builds on the previous. Don't skip to quiz without learning first. Don't skip to sim without cases.
Modes
Parse the user's command to determine mode. Default to learn for new concepts, quiz for concepts already learned.
/master learn [doc-path-or-keyword] — Guided acquisition (start here)
/master quiz [doc-path-or-keyword] — Retrieval practice
/master cases [doc-path-or-keyword] — Case binding
/master sim [doc-path-or-keyword] — Scenario simulation
/master status [doc-path-or-keyword] — Show mastery state
If doc-path-or-keyword is a keyword, search for matching reference docs in the current project or common knowledge base locations. If it's a path, use directly. Works with any reference document — the skill is not tied to a specific topic.
Before Starting Any Mode
- Read the reference document
- Read the mastery state file if it exists (same directory as doc, named
[doc-stem].mastery.json) - Read the cases file if it exists (
[doc-stem].cases.md) - Extract all discrete concepts/frameworks from the doc (each named framework, model, or principle = one concept)
Mode 0: Learn (Guided Acquisition)
Grounded in: Skycak's retrieval practice + WM bottleneck; Chin's "read source practitioners, not summaries" + case pairing
Claude's role: Coach, not textbook. The user reads the source material themselves. Claude assigns what to read, then tests retrieval when they come back.
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.
- 3d ago First seen · 369 lines · 50 tokens per session scan A ff2eaf79b0b9
master is a skill published in the GitHub repository SZoloth/skill-pack (14 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 4,251 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-30.
Other skills, from other repositories
history-autopsy
Only invoke when explicitly requested via "历史速览"、"@history-autopsy" or "history autopsy". Do NOT auto-trigger.
wisdom-decoder
Only invoke when explicitly requested via "智慧解码"、"@wisdom-decoder" or "wisdom decoder". Do NOT auto-trigger.
book-recommender
Only invoke when explicitly requested via "推荐一本书"、"书籍推荐"、"@book-rec" or "book recommendation". Do NOT auto-trigger.
daily-knowledge
Only invoke when explicitly requested via "每日知识"、"@daily-knowledge" or "daily knowledge". Do NOT auto-trigger.
feynman-write
Only invoke when explicitly requested via "@feynman-write"、"费曼写作"、"用费曼写". Do NOT auto-trigger. 费曼写作法:通过费曼逼问让作者自己讲清楚知识点,再整合成博客。适用于想真正搞懂一个主题的学习型写作。AI 做研究整理,作者做知识咀嚼。.
learn-topic
Only invoke when explicitly requested via "学习"、"讲解"、"teach me"、"@learn-topic". Do NOT auto-trigger.