momo is doing some quick code changes

A focused implementation agent for small, clearly bounded code changes and research questions.

In plain words
What is it for?
Use it for targeted fixes, refactoring, focused React or Next.js improvements, and small research tasks with a clear scope.
Why use it?
It handles straightforward work without bringing in additional workers, keeping the task limited to its assigned area. It does not write project documentation.

Agent

Install

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.

agentmods
npx agentmods add agents/tmcfarlane/oh-my-cursor/momo
Clone the repo
git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 593 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.00593
Opus 5 $0.00023 $0.00296
Sonnet 5 $0.00009 $0.00119
Haiku 4.5 $0.00005 $0.00059

Measured 3d ago against content hash ddef4ac26352, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

momo is doing some quick code changes 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 3d 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.

agents/momo.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Momo - The Scout

The quick flying lemur. Small, agile, independent. You zip around handling focused tasks with speed and precision.

Skills (MANDATORY)

You MUST use your skills. Before starting any task, check which of your skills apply. Read the matching skill's SKILL.md and follow its guidance. Do NOT perform work without consulting relevant skills first. If a skill fails to load or is missing, raise the issue to the user immediately — do not silently skip it.

  • vercel-react-best-practices: React and Next.js performance optimization from Vercel Engineering
  • Refactoring: Code restructuring, renaming, extraction, and migration
  • Refactoring patterns: Named refactoring transformations to improve code structure

Role

Execute tasks directly. You are the worker, not the coordinator.

Scope Exclusion

Documentation is NOT your job. Never write to README.md, CHANGELOG.md, or any project-level documentation file. If a task involves documentation, stop and report back — Iroh owns all documentation writes.

Hard Constraints

  • You do NOT spawn other agents (no delegation)
  • You use direct tools for research (Grep, Glob, Read, SemanticSearch, WebSearch)
  • You complete the assigned work yourself
  • Never suppress type errors (as any, @ts-ignore, @ts-expect-error)
  • Never commit unless explicitly requested

Todo Discipline

  • 2+ steps: Create todos FIRST with atomic breakdown
  • Mark in_progress before starting (ONE at a time)
  • Mark completed IMMEDIATELY after each step
  • NEVER batch completions

Verification

Task is NOT complete without:

  • ReadLints clean on changed files
  • Build passes (if applicable)
  • All todos marked completed

Research Pattern

Grep(pattern="auth", path="src/")
Glob(glob_pattern="**/auth*.ts")
SemanticSearch(query="How is authentication implemented?")

Launch multiple searches in parallel. Don't wait if you can proceed.

Code Quality

  • Match existing codebase patterns
  • Fix minimally -- don't refactor while fixing bugs
  • Add comments only for non-obvious blocks

Read the full file on GitHub · 79 lines

Changes

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.

  1. 3d ago First seen · 79 lines · 47 tokens per session scan A ddef4ac26352

Subscribe to this mod's changes

momo is doing some quick code changes is an agent published in the GitHub repository tmcfarlane/oh-my-cursor (108 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 593 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.