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 penwyp/ClaudePreference --skill explaingit clone --depth 1 https://github.com/penwyp/ClaudePreferenceWrote 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/penwyp/claudepreference/explain)<a href="https://agentmods.dev/skills/penwyp/claudepreference/explain"><img src="https://agentmods.dev/badge/skills/penwyp/claudepreference/explain/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/penwyp/claudepreference/explain"><img src="https://agentmods.dev/badge/skills/penwyp/claudepreference/explain.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.00085 | $0.01050 |
| Opus 5.5 | $0.00034 | $0.00420 |
| Sonnet 5.5 | $0.00017 | $0.00210 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
explain 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain
Explain the target in repository context, not in isolation. Always connect the local code to the surrounding call chain, owning module, upstream inputs, downstream effects, and user-visible responsibility.
Prefer evidence from the codebase. If a claim depends on inference, label it clearly as inference.
Input Decision
- Classify the input: code snippet → locate symbols in repo; file path → read file and expand to callers/callees; symbol name or implicit target → search repo for best match.
- Resolve ambiguity before explaining. If multiple matches, explain the best match and mention the ambiguity briefly.
- Keep scope aligned: a single-function question does not need a subsystem tour.
Analysis Workflow
- Read the target artifact.
- Expand one layer outward.
- Check who imports it, who calls it, what it calls, which config or env values feed it, and what outputs or side effects it produces.
- Place it in project structure.
- Identify whether it is an entry point, adapter, domain service, data model, UI component, CLI command, tool handler, scheduler job, test helper, or glue code.
- Extract the important parameters.
- Prioritize constructor params, function args, config fields, env vars, callback hooks, flags, discriminators, and return objects.
- Explain why those parameters matter.
- State what each important parameter controls, where it comes from, typical values, and what behavior changes when it is absent or changed.
- Summarize the role.
- End with the target's responsibility in one sentence that a new contributor can keep in their head.
What To Explain
- The target's direct responsibility.
- Why it exists in this project.
- Where it sits in the call path or module graph.
- What invokes it and what it invokes.
- What data it consumes and produces.
- Which parameters are key and which are incidental.
- What would break or change if a key parameter changed.
- Whether it is framework boilerplate, business logic, integration glue, or cross-cutting infrastructure.
What ships with it
1 file 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.
- 1mo ago First seen · 89 lines · 85 tokens per session scan A 03fe830b5dc8
explain is a skill published in the GitHub repository penwyp/ClaudePreference (136 stars, last pushed 4mo ago), licensed MIT. It adds 85 tokens to every session and 1,050 once invoked, about $0.0003 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…
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…
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.
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
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.