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/juan294/cc-rpi/explore-releasegit 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.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.01329 |
| Opus 5 | $0.00000 | $0.00665 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploratory Release Charters
Model tier: opus — Opus session for the orchestrator. Charter agents run as
parallel general-purpose background Tasks; tier them by cost (sonnet is usually
sufficient for a single charter's execution).
Independent, fresh-context exploratory testing of a fixed release candidate. This
is Wave B of the E2E Pro release-verification system
(templates/e2e-pro-playbook-template.md) — the cheap, high-yield layer that
targets interaction and recovery failures deterministic suites miss.
It complements, and does not replace:
/pre-launch+/remediate— static, code-as-written audit. Charters exercise the deployed candidate's behavior instead./release— the tagging authority. Charters feed evidence into the release gate; they never tag.
Read templates/e2e-pro-playbook-template.md Section 6 (Wave B) for the full
decision detail. This command is the executable protocol.
Input
/explore-release <LAST_RELEASE_REF> <CANDIDATE_SHA_OR_DIGEST>
If arguments are omitted, infer <LAST_RELEASE_REF> from the last release tag and
<CANDIDATE_SHA> from the fixed candidate under release. Confirm both with the
user before spawning agents — a charter run against the wrong candidate is wasted.
Step 1: Fix the candidate and read the diff
-
Confirm the candidate is immutable (a specific SHA, tag, or artifact digest), not a moving branch. Stop if it is mutable (playbook D06).
-
Compute the change surface:
git log --oneline <LAST_RELEASE_REF>..<CANDIDATE_SHA> git diff --stat <LAST_RELEASE_REF>..<CANDIDATE_SHA> -
Map changed paths to user-facing capabilities, actors, surfaces, states, and external seams. Do not trust stale docs — inspect the actual routes, jobs, and providers touched.
Step 2: Generate charters
Size the charter set to the diff — do not pad the count:
- tiny, isolated diff → 1 charter;
- normal release → 2–4 charters;
- more only for distinct high-risk capability groups.
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 · 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 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,329 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
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
commit
智能生成 Git 提交信息并提交.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.
requirement-review
需求文档多角色评审（requirement-review）：需求文档 → 7-Agent 并行评审 → 重构高质量需求文档（Runtime 受控流程，0-7 阶段状态机）.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.