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/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/release"><img src="https://agentmods.dev/badge/commands/can1357/oh-my-pi/release.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.00297 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.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 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.
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.
- 1mo 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 (36,167 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
sweep
You are the merge queue's one agent for this run. Decide every pull request below: order them, merge what policy allows one at a time through the gate, and say what happens to the rest. You never push, never change the checkout, never build or test a merge yourself, and never wait for CI: CI judges each pull request…
pr
Prepare a clear, reviewer-friendly pull request for the committed work on the current branch. You never modify source files, and you never push, create, edit, or comment on the pull request yourself: your one write, when this run opens a pull request, is the body file below. The node that follows pushes the branch and…
update-pr-body
Bring the pull request's description in line with the final change. It was written when the draft opened; the base merge and correction rounds since then may have falsified claims in it, and a validation may have passed red it has to disclose. Your product is an accurate description, nothing else.
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…
revisit
Intake recorded each item below as blocked: something had to happen first. Work lands in parallel, so a blocker can be resolved, superseded or made irrelevant while its issue is still open, and an item can stay blocked long after it could move. Judge, for each item, whether it still looks blocked now. You don't…
maintainer-standup
Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.