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-recapgit 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-recap)<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-recap"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-recap/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-recap"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-recap.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.00047 | $0.02491 |
| Opus 5 | $0.00023 | $0.01246 |
| Sonnet 5 | $0.00009 | $0.00498 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
oma-recap 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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Tool Conversation History Summary
Analyze AI tool conversation histories for a given period and generate themed work summaries.
Scheduling
Goal
Collect AI tool conversation history for a date or window and synthesize it into a themed, project-oriented recap with saved Markdown output.
Intent signature
- User asks for daily recap, weekly/monthly summary, standup notes, work log, tool usage pattern, or AI conversation history analysis.
- User wants conversation histories grouped by work content rather than raw chronological logs.
When to use
- Summarizing a day or period of work activity
- Understanding the overall flow of work across multiple AI tools
- Analyzing tool-switching patterns between sessions
- Preparing daily standups, weekly retros, or work logs
When NOT to use
- Git commit-based code change retrospective -> use
oma retro - Real-time agent monitoring -> use
oma dashboard terminal - Productivity metrics -> use
oma stats get
Expected inputs
- Date, relative date, time window, or tool filter
- Conversation history available through
oma recap --jsonor fallback sources - Desired daily or multi-day recap scope
Expected outputs
- Markdown recap saved to
.agents/results/recap/{date}.mdor range filename - TL;DR, overview, themes/projects, miscellaneous or side projects, and tool usage patterns
- User-facing summary in configured response language
Dependencies
oma recap --json- Optional Claude fallback history at
~/.claude/history.jsonl .agents/oma-config.yamlfor language behavior
Control-flow features
- Branches by date resolution, window length, available tool history, and daily vs multi-day output shape
- Reads local history data and writes Markdown recap files
- Groups by content, not by tool
Structural Flow
Entry
- Resolve requested date or window.
- Collect normalized conversation history.
- Decide daily versus multi-day output structure.
Scenes
- PREPARE: Resolve time range and tool filters.
- ACQUIRE: Collect history through CLI or fallback; retain completion evidence where available.
- REASON: Group by content and classify each item as requested, in progress, or completed from its evidence.
- ACT: Write recap Markdown in the required format.
- VERIFY: Check that every completion claim has direct evidence, then check grouping, language, and output path.
- FINALIZE: Save and display summary.
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.
- yesterday Changed · +2 lines 54b4cf8aca38
- 4d ago Changed fe2cf7a4abad
- 11d ago First seen · 240 lines · 47 tokens per session scan A c5e2e5f297fa
oma-recap is a skill published in the GitHub repository first-fluke/oh-my-agent (1,283 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,491 once invoked, about $0.0002 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
reggeli-napindito
Reggeli összefoglaló: email, naptár, AI hírek, plus Dream Engine top-of-message.
folyamatos-ellenorzes
Ellenorizd: 1) Naptar - van-e meeting 1 oran belul? 2) Email - jott-e surgos level az elmult oraban? 3) Kanban - van-e mai hataridovel kartya? Ha BARMIT talalsz ami fontos, szolj a beallitott csatornan tomoren. Ha minden csendes, ne irj semmit.
generate-daily-schedule
Use when turning a day's structured inputs — fixed commitments, tasks, and free windows — into a concrete 15-minute schedule. Domain-agnostic; the caller provides all context.
mailbox
A guide for performing email and mailbox tasks through the QwenPaw mailbox system. It covers supported personal email providers, credentials, configuration, and the required mailbox workflow.
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.