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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/can1357/oh-my-pinpx agentmods add commands/can1357/oh-my-pi/releaseWrote 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/release)<a href="https://agentmods.dev/commands/can1357/oh-my-pi/release"><img src="https://agentmods.dev/badge/commands/can1357/oh-my-pi/release.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.00297 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
release 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 7d 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.
What it actually says
Release
Release all packages at specified version.
Arguments
$ARGUMENTS: semver version, e.g. 3.13.0.
Version
- Last release: latest git tag (
vX.Y.Z); confirm matchespackages/*/package.jsonversions. - No version: review commits since last tag; choose major/minor/patch; bump.
major/minor/patch: bump last tag — majorX+1.0.0; minorX.Y+1.0; patchX.Y.Z+1.
Run
bun scripts/release.ts $ARGUMENTS
Script automatically:
- Pre-flight: clean working dir; main branch.
- Update all
package.jsonversions. - Regenerate
bun.lock. - Update CHANGELOGs:
[Unreleased] → [version] - date. - Commit and tag.
- Push to origin.
- Watch CI until all workflows pass.
CI failures
CI failure → script exits with error. Fix, then repeat until CI passes:
git commit -m "fix: <brief description>"
git push origin main
git tag -f v$ARGUMENTS && git push origin v$ARGUMENTS --force
bun scripts/release.ts watch
watch: re-watches CI for current commit until all checks pass.
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.
- 7d ago First seen · 42 lines · 0 tokens per session scan A 5f293f9ee024
release is a command published in the GitHub repository can1357/oh-my-pi (29,719 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 297 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
pr
Create a clear, reviewer-friendly pull request for the committed work on the current branch. The PR itself is the artifact — produce no separate report. You never modify source files; your writes are git push and the PR. Every fact belongs in the PR title and body.
sync-pr-body
Bring the pull request description back in line with the code after correction rounds changed it. The description was written when the draft PR opened; corrections since then may have falsified specific claims in it. Your product is an accurate PR body — nothing else.
maintainer-standup
Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.
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).
maintainer-review-comment-quality
Review the PR's added/modified comments and docstrings for accuracy, value, and long-term maintainability (Pi-tuned).