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/wenqingyu/ralphy-openspec/ralphy-archivegit clone --depth 1 https://github.com/wenqingyu/ralphy-openspecWrote 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/wenqingyu/ralphy-openspec/ralphy-archive)<a href="https://agentmods.dev/commands/wenqingyu/ralphy-openspec/ralphy-archive"><img src="https://agentmods.dev/badge/commands/wenqingyu/ralphy-openspec/ralphy-archive.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.00000 | $0.00141 |
| Opus 5 | $0.00000 | $0.00071 |
| Sonnet 5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
ralphy-archive 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 5d 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
/ralphy-archive (Archive completed change)
You are archiving a completed OpenSpec change.
Preconditions
- All tasks are complete
- Tests are green
- Spec deltas reflect final behavior
Steps
- Run tests to confirm green.
- If OpenSpec CLI is available, archive via:
openspec archive <change-name> --yes
- Otherwise, move the change folder from:
openspec/changes/<change-name>/to:openspec/archive/<change-name>/
- Confirm
openspec/specs/is updated appropriately.
Output
Provide a short summary and a test plan.
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.
- 5d ago First seen · 23 lines · 0 tokens per session scan A 0b5c9fc20d18
ralphy-archive is a command published in the GitHub repository wenqingyu/ralphy-openspec (182 stars, last pushed 7mo ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 141 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
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Prepare a release by updating docs and bumping the version.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.