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/first-fluke/fullstack-starter/oma-explanationnpx 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.svg" alt="Measured on agentmods" 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 | $0.00094 | $0.02283 |
| Opus 5 | $0.00047 | $0.01141 |
| Sonnet 5 | $0.00019 | $0.00457 |
| Haiku 4.5 | $0.00009 | $0.00228 |
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 today.
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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oma-explanation — Interactive HTML Code-Change Explainer
Scheduling
Goal
Generate an educational, self-contained interactive HTML document that explains a code change to
a reader — deep skippable background for newcomers, core intuition with toy data, a comprehension-
ordered code walkthrough, and a five-question quiz — saved under .agents/results/explain/ and
validated against a deterministic checklist.
Intent signature
- User invokes
/explain, names this skill, or asks for a rich explanation/walkthrough of a diff, PR, branch, or commit range (설명서, 해설, コード解説, 代码讲解). - Another skill or workflow delegates "explain this change 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
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
Expected inputs
- Target ref, resolved in this order:
- Explicit argument — PR number (
#640, viagh pr diff), branch (git diff main...{branch}), or SHA range (a..b/a...b) - Staged changes (
git diff --cached) - Dirty working tree (
git diff) - Fallback
HEAD~1..HEAD
- Explicit argument — PR number (
- Reader level:
onboarding(default — full deep background) |reviewer(condensed background) - Output language: i18n-guide order — prompt language →
.agents/oma-config.yamllanguage→ en. Prose and quiz in the user's language; code, identifiers, and inline code always English. - Quiz question count: default 5; changed only on explicit request.
What ships with it
2 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.
- today 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 (222 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 2,283 once invoked, about $0.0005 per session on Opus 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
python-patterns
Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
md-to-codelab-html
Converts one or more markdown (.md) source files into a complete, self-contained single-page HTML codelab. Outputs a Google Codelabs-style layout: numbered step sidebar, dynamic screenshot/image injection (referenced by name in markdown, automatically resolved from image files), syntax-highlighted code blocks…
copilotkit-self-update
Use when the user wants to update, refresh, or reinstall the CopilotKit agent SKILLS (the SKILL.md files that teach this agent about CopilotKit). NOT for updating the CopilotKit codebase or project — this is specifically about refreshing the skills/knowledge this agent has loaded. Triggers on "update copilotkit…
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.
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.