Oh My Pi is a coding agent with an integrated development environment, command-line interface, tools, language-server operations, and debugger operations. It is used by developers who want an AI coding assistant that can read and edit projects, work with models from multiple providers, and interact with development tools. The catalogue add-ons extend its agent workflows with skills, commands, agents, plugins, MCP, and instructions.
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 agentmods add commands/can1357/oh-my-pi/fix-issuesgit clone --depth 1 https://github.com/can1357/oh-my-piWrote 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/commands/can1357/oh-my-pi/fix-issues)<a href="https://agentmods.dev/commands/can1357/oh-my-pi/fix-issues"><img src="https://agentmods.dev/badge/commands/can1357/oh-my-pi/fix-issues.svg" alt="Measured on agentmods" 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.00000 | $0.01369 |
| Opus 5 | $0.00000 | $0.00685 |
| Sonnet 5 | $0.00000 | $0.00274 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
fix-issues 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 6d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Issues Command
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
Arguments
$ARGUMENTS optional: space/comma-separated issue numbers/URLs, or GitHub-search qualifiers (is:open, label:bug, author:foo, ...) and/or time window (3d, 2w, 12h).
No issues/flags → all issues open and created within last 3 days.
1. Resolve issues
Parse $ARGUMENTS.
-
Explicit numbers/URLs: use verbatim.
-
Otherwise
githubop: search_issues. No args:github { op: "search_issues", query: "is:open", since: "3d", limit: 50 }User qualifiers verbatim in
query; addis:openunless present. Time window (3d,2w,12h, ISO date; seegithubdocs) →since.dateFielddefaultscreated; set"updated"only for explicitly requested recently-touched issues.
Print resolved set before fan-out for scope confirmation.
2. Parallel subagents
Use parallel task subagents: one/issue. Assignment: number, title, body summary, workflow below. Isolated work; irc only if issues clearly touch the same file.
Each subagent MUST:
a. Read
- Read
issue://<N>; cross-repo:issue://<owner>/<repo>/<N>. Includes body/comments; comments often contain repro/fix hints. Append?comments=0only to explicitly skip comments. - Run
gh search prsfor issue number. Reasonable existing PR → review per.omp/commands/review-prs.md, reportexisting-pr; do NOT create competing fix.
b. Diagnose/reproduce
MUST reproduce in current cwd on main, before any worktree.
- Read relevant checkout source; state concrete 1–2-sentence failure hypothesis.
- Under affected package, create focused
repro-issue-<N>-<slug>.test.ts(or.rs, etc.): unique, greppable, deletable. - Run only that file, never suite; confirm expected failure.
- Reproduced → c.
- Not reproduced → stop; delete test; report
unreproduced: hypothesis, non-failure evidence, unblockers (versions, OS, config, author repro snippet). No worktree/commit. - Out-of-scope/not bug (user-config error, intended behavior, dup) → stop; report
not-a-bugwith issue-postable explanation.
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.
- 6d ago First seen · 137 lines · 0 tokens per session scan A adc70ef49124
fix-issues is a command published in the GitHub repository can1357/oh-my-pi (29,519 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,369 tokens. 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 commands, from other repositories
handoff
Write a session handoff document for the next agent or session.
maintainer-review-test-coverage
Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).
implement-fix
Implement fix from RCA document for GitHub issue.
prime-isolation
Prime agent with Archon isolation system and git operations context.
maintainer-review-error-handling
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
commit
Create an atomic commit for current changes.