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-skill-creationgit 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-skill-creation)<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-skill-creation"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-skill-creation/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-skill-creation"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-skill-creation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 105 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00072 | $0.01187 |
| Opus 5 | $0.00036 | $0.00593 |
| Sonnet 5 | $0.00014 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
oma-skill-creation 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- oma-skill-creation — 100% identical, 181 lines differ
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMA Skill Authoring
Scheduling
Goal
Create or revise a usable OMA skill with clear routing, one execution path, domain-specific recovery, and proportionate context.
Intent signature
- Create, update, audit, or normalize an OMA skill, its resources, or the SSL-lite format.
- Decide whether content belongs inline, in a conditional resource, or should be removed.
When to use
- Authoring
.agents/skills/{name}/SKILL.mdand supporting resources. - Reviewing skill routing, execution contracts, reference loading, or duplicated instructions.
When NOT to use
- Installing third-party skills -> skill installer; creating a Codex plugin -> plugin tooling.
- Application implementation -> the owning specialist; project requirements ->
oma-pm.
Expected inputs
Skill purpose, triggers, boundaries, execution model, and existing commands/resources or user edits to preserve.
Expected outputs
A four-section SKILL.md, only necessary supporting resources, and validation results with unresolved limitations.
Dependencies
resources/ssl-lite-template.md for the skeleton and resources/validation-checklist.md for acceptance criteria. Use native file tools and available oma skill validators. Follow repository rules for source ownership and generated copies.
Structural Flow
Transitions
- New skill: compare 1–3 analogous skills, then use the template.
- Existing skill: preserve working domain detail and change only the requested scope.
- Repeated instructions: retain one authoritative location and a short reference where independently invoked entry points need it.
- Long or conditional detail: move to a named resource with a load condition. Do not move a duplicate merely to keep it elsewhere.
- Machine-checkable artifacts: declare structured
outputs:as documented in the template.
Failure and recovery
| Failure | Recovery |
|---|---|
| Overbroad routing | Narrow triggers and add a concrete When NOT to use cross-route |
| Vague execution | Add actual objects, paths, command flags, and evidence to the canonical path |
| Repeated procedure in multiple sections | Keep the canonical procedure; retain only distinct branches or state transitions elsewhere |
| Required tool unavailable | Use the documented fallback; otherwise report which result cannot be verified |
| Conflicting source and generated copies | Use the repository's generation flow; do not hand-edit protected definitions |
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 Changed · -85 lines ade25c73447d
- 4d ago Changed 41983fe1d865
- 10d ago First seen · 171 lines · 72 tokens per session scan A ad0525de3ff6
oma-skill-creation is a skill published in the GitHub repository first-fluke/oh-my-agent (1,278 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,187 once invoked, about $0.0004 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.
ai-fleet-project-execution
AI fleet project execution (orchestrator=PM, marketing agent, backend dev agent, video agent). Fast-iteration architecture pivots and inter-agent task delegation across multi-hour sessions. Use when a user assigns a multi-agent project with "take it as a team" instruction.
github-pr-rebase-merge
Merge a stack of GitHub PRs sequentially when they share files and will cause cascading conflicts. Triggers when user says "merge the PRs sorban" or similar, and the PRs come from external forks (cannot push back to PR branch).
memoria-heartbeat
Minden körben átnézi az ELŐZŐ KÖR ÓTA történteket, menti a fontosat, és skill-eket generál ha volt komplex munka.
handoff
Generate a HANDOFF.md context transfer document for session continuity. Use when switching sessions, handing off to another agent, or preserving complex task context before a context window reset. Trigger on "/handoff" command or "handoff:" prefix in inter-agent messages.
approval-request-handling
A fő-ágens eljárása, amikor egy sub-ágens jóváhagyást kér az approval API-n keresztül ([APPROVALREQUEST] inter-agent üzenet). Kiküldi a kérést a tulajdonosnak, feldolgozza a szöveges válaszát, és lezárja az approvalt. Akkor használd, ha [APPROVALREQUEST] kezdetű inter-agent üzenetet kapsz.