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-brainstormgit 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-brainstorm)<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-brainstorm"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-brainstorm/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-brainstorm"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-brainstorm.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.00029 | $0.02440 |
| Opus 5.5 | $0.00012 | $0.00976 |
| Sonnet 5.5 | $0.00006 | $0.00488 |
| Haiku 4.5 | $0.00003 | $0.00244 |
Grade A, and why
oma-brainstorm 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- oma-brainstorm — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm - Design-First Ideation
Scheduling
Goal
Explore user intent, constraints, and alternative approaches before planning or implementation, then preserve an approved design for downstream planning.
Intent signature
- User says they have an idea, want to brainstorm, compare approaches, explore concepts, or design before planning.
- Request is ambiguous enough that implementation or task planning would be premature.
When to use
- Exploring a new feature idea before planning
- Understanding user intent and constraints before committing to an approach
- Comparing multiple design approaches with trade-offs
- When the user says "I have an idea" or "let's design something"
- Before invoking
/planfor complex or ambiguous requests
When NOT to use
- Requirements are already clear and well-defined -> use
oma-pmdirectly - Implementing actual code -> delegate to specialized agents
- Performing code reviews -> use
oma-qa - Debugging existing issues -> use
oma-debug
Expected inputs
- Early idea, ambiguous goal, product concept, design question, or set of constraints
- Existing project context when the idea must fit a codebase or product direction
- User preferences and approval gates
Expected outputs
- Clarified intent and constraints
- Viable approaches as prose briefs (scenario, mechanism, residual risk), with comparison and recommendation when alternatives aid the decision
- Section-by-section approved design document
- Blind-review issue list (Tier 1 resolved, Tier 2/3 resolved or explicitly deferred)
- Saved design artifact before handoff to planning
Dependencies
- Shared context loading, reasoning templates, clarification protocol, quality principles, and skill routing
- Optional
resources/triz-lite.mdfor contradiction-shaped approach seeding - Per-agent reviewer dispatch (e.g.
qa-reviewer,architecture-reviewer) for the high-stakes blind-review escalation path - Downstream PM workflow for task decomposition after design approval
What ships with it
1 file 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.
- 12d ago Changed 0a33dc513b42
- 23d ago Changed 5c8df89acfea
- 25d ago Changed aa1cd95c023c
- 1mo ago Changed · -2 lines · -9 tokens per session 4716f6c47d1c
- 1mo ago Changed · -1 lines cd9777f29f32
- 1mo ago Changed 1cd5cf3560df
- 1mo ago Changed 3d52bf5d0a98
- 1mo ago First seen · 168 lines · 38 tokens per session scan A c509c805475d
oma-brainstorm is a skill published in the GitHub repository first-fluke/oh-my-agent (1,354 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 2,440 once invoked, about $0.0001 per session on Opus 5.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.
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.
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, a jóváhagyáshoz a dashboardra irányítja (jóváhagyni csak ő tud, bejelentkezve), az elutasítást lezárja. Akkor használd, ha [APPROVALREQUEST] kezdetű…
fleet-helper
Shared, dependency-free Python helpers for the agent fleet - dashboard API (memory, messages, kanban), Telegram MarkdownV2 escaping, and rule-based Mail.app triage. Use to do deterministic work (fetch/filter/SQL/format/escape) in Python instead of burning model tokens doing it in the LLM turn. The dashboard token is…
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).