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.
git 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/review-prs)<a href="https://agentmods.dev/commands/can1357/oh-my-pi/review-prs"><img src="https://agentmods.dev/badge/commands/can1357/oh-my-pi/review-prs/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/commands/can1357/oh-my-pi/review-prs"><img src="https://agentmods.dev/badge/commands/can1357/oh-my-pi/review-prs.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.00000 | $0.01257 |
| Opus 5.5 | $0.00000 | $0.00503 |
| Sonnet 5.5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
review-prs 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PRs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
Arguments
$ARGUMENTS optional:
- space/comma-separated PR numbers/URLs; or
- GitHub-search qualifiers (
is:open,author:foo,label:bug,draft:false, ...) and/or time window (3d,2w,12h).
No PRs or flags: all open PRs opened in last 3 days.
1. Resolve PRs
Parse $ARGUMENTS. Explicit numbers/URLs: use verbatim. Otherwise github op: search_prs; no-args default:
github { op: "search_prs", query: "is:open", since: "3d", limit: 50 }
Pass supplied qualifiers verbatim in query; add is:open unless present. Time window (3d, 2w, 12h, ISO date; see github docs): since. dateField defaults created; set "updated" only on explicit request for recently-touched PRs. Print resolved set before fan-out for scope confirmation.
2. One parallel task subagent/PR
Assign each PR's number, head ref, author, and workflow. Agents isolate; use irc only if a fix on PR A obviously conflicts with PR B.
Required subagent workflow
Read and decide
- Read
pr://<N>(comments default;?comments=0skips) andpr://<N>/diff(changed-file listing). Full unified diff:pr://<N>/diff/all; file slice:pr://<N>/diff/<i>. - Check
git log origin/mainandgh search prsfor an already-landed equivalent. - Decision:
slop: AI-generated noise, broken, off-spec, or net-negative. Drop; 1–2-line justification; no checkout.superseded: fixed/merged in main or newer PR. Drop with pointer.worthy: proceed.
Ambiguous: worthy; human decides on a real branch.
Checkout
gh_PR=<NUMBER>
# pr_checkout creates ~/.omp/wt/<encoded-repo>/pr-<N>/ and configures push remote
MUST use github pr_checkout, not raw gh pr checkout: it creates a dedicated worktree wired for later pr_push.
Symlink build artifacts
Before any worktree build/test, from the worktree symlink main-checkout outputs to avoid bun check / cargo build / native-loader recompilation:
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 · 129 lines · 0 tokens per session scan A 03edc7f6df3c
review-prs is a command published in the GitHub repository can1357/oh-my-pi (36,840 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,257 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
settle-threads
The previous round read unresolved review threads on the pull request, and this round's implementer judged each one like a review finding: fixed it, declined it with evidence, or found it needs a decision this run cannot make. Decide which threads are settled and write the reply each one gets. You write nothing…
review-scope
Establish exactly what this review round examines, and write it down for the reviewer or reviewers that follow. You do not judge anything; you make the target precise.
maintainer-review-code-review
Review the PR for code quality, CLAUDE.md compliance, project conventions, and bugs (Pi-tuned).
maintainer-review-docs-impact
Review whether the PR's user-facing changes (APIs, CLI flags, env vars, behavior) are reflected in documentation (Pi-tuned).
maintainer-review-synthesize
Synthesize findings from all review aspects into a single maintainer-ready review report (Pi-tuned).
maintainer-review-comment-quality
Review the PR's added/modified comments and docstrings for accuracy, value, and long-term maintainability (Pi-tuned).