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/juan294/cc-rpiWrote 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/juan294/cc-rpi/explore-release)<a href="https://agentmods.dev/commands/juan294/cc-rpi/explore-release"><img src="https://agentmods.dev/badge/commands/juan294/cc-rpi/explore-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/juan294/cc-rpi/explore-release"><img src="https://agentmods.dev/badge/commands/juan294/cc-rpi/explore-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.00154 |
| Opus 5.5 | $0.00000 | $0.00062 |
| Sonnet 5.5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
explore-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
Legacy command renamed
This legacy command is a rename notice only. Its workflow is now rpi-explore-release.
- Claude direct installation: invoke
/rpi-explore-release. - Claude plugin installation: invoke
/cc-rpi:rpi-explore-release. - Codex direct installation: invoke
$rpi-explore-releaseor select the skill. - Codex plugin installation: use the actual selector recorded by package diagnostics.
Report this rename and stop. Do not auto-forward, bypass invocation controls or execute an old workflow body. New installations do not add this legacy alias. Existing managed aliases may retain this explicit-only notice during the 2.x compatibility period; custom aliases remain user-owned.
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 Changed · -116 lines ec0b5a16846e
- 1mo ago First seen · 134 lines · 0 tokens per session scan A f343d83d2994
explore-release is a command published in the GitHub repository juan294/cc-rpi (5 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 154 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-31.
Other commands, from other repositories
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
4-close-project
Name: 4-close-project Purpose: Apply an OpenSpec change through TDD, verify it, prepare or update the PR, and leave archive for after merge.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
release-check
Run the release-readiness umbrella + draft a tweet-length announcement.