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/shaun0927/opensafari/release-osgit clone --depth 1 https://github.com/shaun0927/opensafariWrote 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/shaun0927/opensafari/release-os)<a href="https://agentmods.dev/commands/shaun0927/opensafari/release-os"><img src="https://agentmods.dev/badge/commands/shaun0927/opensafari/release-os.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 | $0.00023 | $0.03337 |
| Opus 5 | $0.00012 | $0.01669 |
| Sonnet 5 | $0.00005 | $0.00667 |
| Haiku 4.5 | $0.00002 | $0.00334 |
Grade C, and why
release-os scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.npm/_npx/*/node_modules/opensafari-mcp How it starts
The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSafari Release Workflow
$ARGUMENTS
STEP 1: Status Check
Run all of these and report results:
git status
git stash list
git branch -a
gh pr list --state open --json number,title,headRefName,baseRefName,additions,deletions,author,files
npm run build
npm run lint
npm test
Gate: If build, lint, or tests fail, fix errors first. Do NOT proceed with any failures.
STEP 2: Classify Open PRs
For each open PR, determine ownership:
| Type | How to Identify | Action |
|---|---|---|
| MY PR | author.login matches repo owner |
Review → Fix P0/P1 → Merge |
| OTHER's PR | Different author | Review → Post comment → Do NOT merge |
List all PRs in a table (include mergeable status):
# Get mergeable status for all open PRs
gh pr list --state open --json number,mergeable,mergeStateStatus \
--jq '.[] | "\(.number) | \(.mergeable) | \(.mergeStateStatus)"'
| PR # | Title | Author | Type | Files Changed | Mergeable |
|------|-------|--------|------|---------------|-----------|
STEP 3: Triage Local Changes
Check for uncommitted local work:
git status
git stash list
git diff --stat
For each local change, classify:
| Change Type | Action |
|---|---|
Source code (.ts) changes |
Create PR by category (feat/fix/refactor/chore). All PR titles, descriptions, and commit messages MUST be in English. |
.claude/ agents/commands |
Validate YAML frontmatter, bundle into chore PR |
| Temp/experiment files | Delete if not needed |
| Stashed changes | Pop, resolve conflicts, commit or drop |
Gate: All local changes committed or discarded. git status shows clean working tree.
STEP 4: Review Each PR
For EACH open PR (both mine and others'), in order:
4a. Run /pr-review-os <N>
This produces a P0/P1/P2 issue list and verdict.
4b. Take action based on ownership + verdict
MY PR with P0s:
git checkout <branch>- Fix ALL P0 issues
npm run build— must pass- Commit and push fixes
- Re-run
/pr-review-os <N>— must have P0 = 0 - If P1s remain, fix those too
- Repeat until P0 = 0 and P1 = 0
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.
- 4d ago First seen · 378 lines · 23 tokens per session scan C 672d3e5f74f0
release-os is a command published in the GitHub repository shaun0927/opensafari (15 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 3,337 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
ship
Deliver the increment. Then go live with a rollback you have run.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
release-tag
Create and push a version tag after a release PR has been merged.
release
Orchestrate a complete release workflow with quality gates, version bumping, and publishing automation.