oh-my-agent is a harness for checking whether coding agents actually completed their work by verifying tests, required artifacts, independent reviews, and recorded decisions. It is used across multiple agent runtimes to make workflow results auditable instead of relying on an agent's own report. The catalogue add-ons provide parts of its skills, agents, hooks, MCP integrations, instructions, and plugins.
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/oh-my-agent --skill oma-explanationgit clone --depth 1 https://github.com/first-fluke/oh-my-agentWrote 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/oh-my-agent/oma-explanation)<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-explanation"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/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/oh-my-agent/oma-explanation"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-explanation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.02415 |
| Opus 5 | $0.00047 | $0.01208 |
| Sonnet 5 | $0.00019 | $0.00483 |
| Haiku 4.5 | $0.00009 | $0.00242 |
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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- oma-explanation — 100% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 185 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.
- yesterday Changed · +5 lines e27425bcc009
- 11d ago First seen · 180 lines · 94 tokens per session scan A f93348c15824
oma-explanation is a skill published in the GitHub repository first-fluke/oh-my-agent (1,283 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 2,415 once invoked, about $0.0005 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
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
guidance
A guide for answering questions about installing and configuring QwenPaw, a software tool with local documentation. It says to check those documents first and use official website information only when needed.
edu-math-tutorial
A Chinese-language guide for turning a maths problem into a step-by-step teaching video. It explains how to break down the solution, write narration, format equations, and structure scenes.
llmtornado-tutorial-generator
Generates comprehensive code tutorials on LlmTornado API formatted for Medium publication with examples, explanations, and best practices.
aiwg-guide
Contextual AIWG help — explains current version features, answers how-to questions, routes live queries to the steward.
aiwg-help
Display all available AIWG CLI commands, their arguments, and usage examples.