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-searchgit 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-search)<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-search"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-search/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-search"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-search.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.00061 | $0.01107 |
| Opus 5 | $0.00030 | $0.00553 |
| Sonnet 5 | $0.00012 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
oma-search 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
2 near-identical copies found in the catalogue:
- oma-search — 100% identical, 185 lines differ
- oma-search — 91% identical, 190 lines differ
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Router
Scheduling
Goal
Route an information request to the appropriate channel and return relevant sources with trust labels.
Intent signature
- Search, find, look up, reference docs, inspect official APIs, or search remote code.
- Another skill requests docs, web, code, or local search with a query and constraints.
When to use
- Library documentation, web research, GitHub/GitLab implementation patterns, or unclear search channels.
When NOT to use
- Pure local code exploration -> use configured code intelligence under the shared contract.
- Git history/blame ->
oma-scm; architecture analysis ->oma-architecture.
Expected inputs
Query, optional route hint (docs, web, code, local), source/recency constraints, and flags. Explicit --docs, --code, or --web selects the route; --strict filters trust, --wide retains labeled results, and --gitlab selects the remote code host.
Expected outputs
Ranked sources with URL or file reference, route, relevance, trust level/score, and material fallback limits. Do not invent sources when no reliable result is found.
Dependencies
Context7 for docs, runtime web search, oma search/gh/glab for remote code, and configured code intelligence or native local search.
Structural Flow
Routes
| Route | Primary | Fallback | Use for |
|---|---|---|---|
docs |
Context7 resolve-library-id → query-docs |
Web search | Official API/framework documentation |
web |
Runtime web search | oma search fetch <url> for known result URLs |
Web sources |
code |
oma search code |
Report unavailable host/auth | Remote repository patterns |
local |
Configured code-intelligence provider | Native search and scoped reads | Current project files and symbols |
Failure and recovery
- Missing/empty documentation lookup: use web search and state the fallback.
- A known URL cannot be fetched: use the fetch strategies in the route reference; retain authentication/blocking errors if all strategies fail.
- Configured local tools unavailable or timed out: follow
../_shared/core/code-intelligence.md. - Unknown trust: retain the result as
unknownwith score—; do not imply verification. - No result satisfies
--strict: report that outcome and offer a wider or narrower query.
What ships with it
6 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 · -91 lines · +2 tokens per session 0d920eef70ab
- 4d ago Changed d3f42ef089f8
- 11d ago First seen · 179 lines · 59 tokens per session scan A 2d9fc15e17bb
oma-search is a skill published in the GitHub repository first-fluke/oh-my-agent (1,283 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 1,107 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
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.