Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jinseo-jang/antigravity-plugin-cc/plugin install agyWrote 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/jinseo-jang/antigravity-plugin-cc/retry)<a href="https://agentmods.dev/commands/jinseo-jang/antigravity-plugin-cc/retry"><img src="https://agentmods.dev/badge/commands/jinseo-jang/antigravity-plugin-cc/retry/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/jinseo-jang/antigravity-plugin-cc/retry"><img src="https://agentmods.dev/badge/commands/jinseo-jang/antigravity-plugin-cc/retry.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.00008 | $0.00411 |
| Opus 5 | $0.00004 | $0.00205 |
| Sonnet 5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
retry 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 8d 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
Retry the session from a failure point using a named retry strategy.
!python "${CLAUDE_PLUGIN_ROOT}/scripts/cao-companion.py" --plugin-data "${CLAUDE_PLUGIN_DATA}" session.retry "$ARGUMENTS"
The command above prints a JSON object with a session_id. Supervise that session
until it finishes, using the Antigravity companion via the Bash tool:
- Watch: run
python "${CLAUDE_PLUGIN_ROOT}/scripts/cao-companion.py" --plugin-data "${CLAUDE_PLUGIN_DATA}" session.wait <session_id>. It blocks up to ~25s and returns a pending approval, "running", or "finished". - If it reports "running", run
session.wait <session_id>again. - If it reports a pending approval, call the AskUserQuestion tool showing the
exact command, with four options: Approve once, Approve for this project,
Approve always, and Deny. Then apply the choice:
- Approve once:
... cao-companion.py session.approve <call_id> - Approve for this project:
... cao-companion.py session.approve <call_id> project - Approve always:
... cao-companion.py session.approve <call_id> global - Deny:
... cao-companion.py session.deny <call_id>"For this project" and "always" remember the EXACT command so identical future commands auto-approve without prompting. Then return to step 1.
- Approve once:
- When it reports the session finished, run
... cao-companion.py session.events <session_id>and show the user the digest.
Never approve or deny on your own — the user decides every approval via AskUserQuestion.
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.
- 8d ago First seen · 32 lines · 8 tokens per session scan A 51ebd455bb62
retry is a command published in the GitHub repository jinseo-jang/antigravity-plugin-cc (6 stars, last pushed 25d ago), licensed Apache-2.0. It adds 8 tokens to every session and 411 once invoked, about $0.0000 per session on Opus 5. 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.