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/triage)<a href="https://agentmods.dev/commands/can1357/oh-my-pi/triage"><img src="https://agentmods.dev/badge/commands/can1357/oh-my-pi/triage/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/triage"><img src="https://agentmods.dev/badge/commands/can1357/oh-my-pi/triage.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.01318 |
| Opus 5.5 | $0.00000 | $0.00527 |
| Sonnet 5.5 | $0.00000 | $0.00264 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
triage 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Command
Classify/label newly opened GitHub issues missing labels.
Arguments
$ARGUMENTS: optional --days <n>; default 7. Triage only open issues created within this window.
Steps
1. Fetch
Parse $ARGUMENTS for --days (default 7).
# Build cutoff date (UTC) for "new" issues
CUTOFF_DATE="$(python - <<'PY'
from datetime import datetime, timedelta, timezone
print((datetime.now(timezone.utc) - timedelta(days=7)).strftime('%Y-%m-%d'))
PY
)"
# Fetch only newly created open issues (default 7-day window)
gh issue list --state open --search "created:>=${CUTOFF_DATE}" --json number,title,body,labels,comments,createdAt --limit 50
2. Candidates
Skip issues older than cutoff or labeled triaged. Of the rest, skip only if all applicable requirements hold:
- Exactly one primary:
bug|enhancement|question|proposal|documentation|invalid|duplicate. bug→ exactly oneprio:*.- Applicable functional scope → at least one:
agent|tool|tui|cli|prompting|sdk|auth|setup|ux|providers. - Provider-specific → matching
provider:*; platform-specific → matchingplatform:*.
3. Classification
For every candidate, read title, body, and all comments; comments may contain critical context. Labels below; primary exactly one, priority exactly one only for bug, functional all applicable. Provider/platform labels require explicit issue evidence.
Primary
bug: broken existing behavior—crash, error, regression, "doesn't work".enhancement: feature request/improvement to existing behavior.question: how-to, clarification, usage question.proposal: design/process proposal needing maintainer decision.documentation: missing, incorrect, outdated docs.invalid: spam, off-topic, not actionable.duplicate: clear duplicate; reference original in a comment.
Bug priority
prio:p0: critical blocker, data loss/security breakage, unusable workflow.prio:p1: high impact, common workflow broken, fix soon.prio:p2: medium impact, workaround exists, not blocking most users.prio:p3: low impact, edge case/minor issue.
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 · 112 lines · 0 tokens per session scan A d460f7b290ad
triage is a command published in the GitHub repository can1357/oh-my-pi (35,561 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,318 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
triage
Confirm whether the work item still names real current work, judge whether it is a contract a run can start from, choose the kind of reasoning owed next, and stop. Write the decisive evidence and handoff to $ARTIFACTSDIR/triage.md. You assess and route only: the repository must be exactly as you found it when you…
maintainer-standup
Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.
investigate
Establish the proven causal chain for the target — from the observed symptom to the root cause that actually explains it — and write a report a fixer or planner can act on without repeating your work. You change nothing and fix nothing: the repository must be exactly as you found it when you finish. No one watches the…
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-synthesize
Synthesize findings from all review aspects into a single maintainer-ready review report (Pi-tuned).