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/ashgithub/ocigeniworkshop/module-docs-explainernpx skills add ashgithub/ocigeniworkshop --skill module-docs-explainergit clone --depth 1 https://github.com/ashgithub/ocigeniworkshopWhat 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.00069 | $0.00290 |
| Opus 5 | $0.00034 | $0.00145 |
| Sonnet 5 | $0.00014 | $0.00058 |
| Haiku 4.5 | $0.00007 | $0.00029 |
Grade A, and why
module-docs-explainer 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 2d 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
Module Docs Explainer
Use this skill to turn repo docs into a clear learning explanation. It is mid-level: load a small reference file when useful, then inspect the actual README or module files before answering.
Workflow
- Read
references/module-map.mdwhen the user asks where a topic lives. - Read
references/explanation-examples.mdwhen the user asks for a learning path, comparison, or module explanation. - Inspect the relevant repo README before giving detailed guidance.
- Explain the module in terms of purpose, best entry docs, runnable examples, prerequisites, and a small practice task.
- Keep file recommendations focused; prefer 3-6 concrete paths over a directory dump.
Output Shape
Return these sections when they fit the request:
What this module teachesBest files to openHow to read itSafe commands to tryWatch outs
Do not invent cloud/API results. If a script needs OCI credentials, say what must be configured before running it.
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.
- 2d ago First seen · 29 lines · 69 tokens per session scan A 26579c6c6d7f
module-docs-explainer is a skill published in the GitHub repository ashgithub/ocigeniworkshop (22 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 69 tokens to every session and 290 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…