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 first-fluke/fullstack-starter --skill oma-explanationgit clone --depth 1 https://github.com/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/oma-explanation)<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-explanation"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-explanation/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/first-fluke/fullstack-starter/oma-explanation"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-explanation.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.00039 | $0.02963 |
| Opus 5.5 | $0.00016 | $0.01185 |
| Sonnet 5.5 | $0.00008 | $0.00593 |
| Haiku 4.5 | $0.00004 | $0.00296 |
Grade A, and why
oma-explanation 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 9d 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.
This is a copy
100% identical to oma-explanation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oma-explanation — Interactive HTML Explainer
Scheduling
Goal
Generate an educational, self-contained interactive HTML document, saved under
.agents/results/explain/ and validated against a deterministic checklist. Two modes:
- Change mode — explains a code change: deep skippable background for newcomers, core intuition with toy data, a comprehension-ordered code walkthrough, and a five-question quiz.
- Topic mode — explains a concept, a system, or the answer to a question as a one-page visual sheet: lead answer, then panels of diagrams, tables, and short prose.
In both modes the model writes a Markdown draft and oma explain render produces the HTML.
Layout, theme, diagram geometry, and the quiz script are the renderer's, not the model's.
Intent signature
- User invokes
/explain, names this skill, or asks for a rich explanation/walkthrough of a diff, PR, branch, or commit range (설명서, 해설, コード解説, 代码讲解). - User asks for a visual / HTML explanation of a topic that is not a diff: how a system works,
a comparison, an answer worth keeping as a page (
/explain how does the row planner work). - Another skill or workflow delegates "explain this as a document" output.
- Activation is slash/explicit/delegated only — this skill is intentionally excluded from
keyword auto-detection ("explain" is everyday vocabulary;
convertprecedent).
When to use
- Explaining a PR, branch, commit range, or the current staged/unstaged change as a document
- Onboarding a teammate onto a change they did not write
- Producing a reviewable teaching artifact after a large or subtle change lands
- Turning an architecture, a protocol, a comparison, or a long answer into one visual page
When NOT to use
- Narrated explainer video → use
oma-video(explainer mode); this skill produces HTML documents - Checking whether docs still match the codebase → use
oma-docs(drift detection) - Presentation deck / slides → use
oma-slide(fixed 1920×1080 deck contract) - Finding defects or issuing review verdicts → use
oma-qa(or thereviewworkflow); this skill narrates a change educationally, it does not evaluate 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.
- 9d ago Changed · +30 lines · +10 tokens per session 8d24fabab8ca
- 22d ago Changed e0d9d18b1548
- 1mo ago Changed · +1 lines · -65 tokens per session 2d79918e1518
- 1mo ago First seen · 180 lines · 94 tokens per session scan A f93348c15824
oma-explanation is a skill published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 2,963 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to oma-explanation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
retro-learn
Convert delivery findings into skill, eval, workflow, and documentation improvements.
system-design-case-catalog
Answer classic system design problems as constraint-to-solution sketches and coach interview practice: URL shortener, rate limiter, news feed, chat, notification, autocomplete, crawler, unique id. Use for interview practice or naming the closest known shape for a new problem.
system-design-interview-coaching
Facilitate timed system-design interview practice across backend, mobile/client, SDK/library, and full-stack surfaces. Use risk-driven probes, an adverse timeline, mechanism revision, one changed constraint, and the existing six-criterion evidence-based debrief.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
billing-stripe
Work with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.
dev-fix
Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.