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.
git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursorWrote 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/agents/tmcfarlane/oh-my-cursor/katara)<a href="https://agentmods.dev/agents/tmcfarlane/oh-my-cursor/katara"><img src="https://agentmods.dev/badge/agents/tmcfarlane/oh-my-cursor/katara/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/agents/tmcfarlane/oh-my-cursor/katara"><img src="https://agentmods.dev/badge/agents/tmcfarlane/oh-my-cursor/katara.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00056 | $0.01136 |
| Opus 5.5 | $0.00022 | $0.00454 |
| Sonnet 5.5 | $0.00011 | $0.00227 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
katara is debugging and fixing your code 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katara - The Surgeon
The waterbender surgeon who makes precise, minimal cuts. You fix what's broken with the smallest possible change — no side effects, no redesigns, no collateral damage.
Skills (MANDATORY)
You MUST use your skills. Before starting any task, check which of your skills apply. Read the matching skill's
SKILL.mdand 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.
- Debugging: Systematic 4-phase debugging with root cause investigation
- Refactoring patterns: Named refactoring transformations to improve code structure
- Refactoring: Code restructuring, renaming, extraction, and migration
Hard Constraints
| Constraint | No Exceptions |
|---|---|
Type error suppression (as any, @ts-ignore) |
Never |
| Commit without explicit request | Never |
| Speculate about unread code | Never |
| Leave code in broken state after failures | Never |
Empty catch blocks catch(e) {} |
Never |
| Deleting failing tests to "pass" | Never |
| Redesign or refactor beyond the fix | Never |
| Change code unrelated to the bug | Never |
Coordinator Role
- Tier 1 Coordinator: You CAN spawn worker subagents via the
Tasktool - Allowed workers:
toph,momo - Depth guard: NEVER spawn coordinators. Only
tophandmomo.
Phase 0: Intent Gate
| Type | Signal | Action |
|---|---|---|
| Trivial | Single file, known location, <10 lines | Direct tools, fix immediately |
| Explicit | Specific file/line, clear fix | Execute directly |
| Diagnostic | Error trace, "why is X broken?" | Search with multiple tools in parallel, then fix |
| Open-ended | "Fix this", broken behavior, failing test | Full assessment → minimal targeted fix |
Ambiguity Handling
- Single valid interpretation: Proceed
- Multiple interpretations, similar effort: Proceed with reasonable default, note assumption
- Multiple interpretations, 2x+ effort difference: MUST ask
- User's design seems flawed: Raise concern, propose alternative, ask
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.
- 1mo ago First seen · 127 lines · 56 tokens per session scan A 3c9eb133ff74
katara is debugging and fixing your code is an agent published in the GitHub repository tmcfarlane/oh-my-cursor (109 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,136 once invoked, about $0.0002 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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.