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 skills/vit129/agy-plugin-cc/agy-cli-runtimenpx skills add Vit129/agy-plugin-cc --skill agy-cli-runtimegit clone --depth 1 https://github.com/Vit129/agy-plugin-ccWhat 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.00018 | $0.01208 |
| Opus 5 | $0.00009 | $0.00604 |
| Sonnet 5 | $0.00004 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
agy-cli-runtime 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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agy Runtime
Use this skill only inside the agy:agy-rescue subagent.
Primary helper:
node "${CLAUDE_PLUGIN_ROOT}/scripts/agy-companion.mjs" task "<raw arguments>"
Execution rules:
- The rescue subagent is a forwarder, not an orchestrator. Its only job is to invoke
taskonce and return that stdout unchanged. - Do not call
setup,review,adversarial-review,status,result, orcancelfromagy:agy-rescue. - Use
taskfor every rescue request, including diagnosis, planning, research, and explicit fix requests. - You may use the
gemini-3-promptingskill to rewrite the user's request into a tighter agy prompt before the singletaskcall. - That prompt drafting is the only Claude-side work allowed. Do not inspect the repo, solve the task yourself, or add independent analysis outside the forwarded prompt text.
Command selection:
- Use exactly one
taskinvocation per rescue handoff. - If the forwarded request includes
--backgroundor--wait, treat that as Claude-side execution control only. Strip it before callingtask, and do not treat it as part of the natural-language task text. - If the forwarded request includes
--resume, strip that token and add--resume-lastto thetaskcall. - If the forwarded request includes
--fresh, strip that token and do not add--resume-last. - If the forwarded request includes
--sandbox, pass it through totask. --resume: always usetask --resume-last, even if the request text is ambiguous.--fresh: always use a freshtaskrun, even if the request sounds like a follow-up.- If the request sounds like a follow-up ("continue", "keep going", "resume", "apply the top fix", "dig deeper"), add
--resume-lastunless--freshis present.
Safety rules:
- Default to write-capable agy work in
agy:agy-rescueunless the user explicitly asks for--sandbox. - Preserve the user's task text as-is apart from stripping routing flags.
- Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any follow-up work of your own.
- Return the stdout of the
taskcommand exactly as-is. - If the Bash call fails or agy cannot be invoked, return nothing.
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.
- 2d ago First seen · 58 lines · 18 tokens per session scan A c0ab2db6aeb3
agy-cli-runtime is a skill published in the GitHub repository Vit129/agy-plugin-cc (5 stars, last pushed 9d ago), licensed MIT. It adds 18 tokens to every session and 1,208 once invoked, about $0.0001 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 skills, from other repositories
ag-sdd
Activates the Anti-Gravity Spec-Driven Development (ag-sdd) workflow. Use this skill when the user asks to implement a feature, fix a bug, or write code in a repository that uses ag-sdd. It enforces a strict 4-phase SDD lifecycle: Discovery, Spec Generation, Sequential Execution, and Quality Signoff.
collaborating-with-antigravity
Delegate analytical, sandboxed, or long-running work to the Google Antigravity (agy) CLI through a JSON-bridge wrapper. Use when you need a second opinion, want to isolate side effects in a worktree, or need to run a long agent loop without blocking the main conversation.
collaborating-with-antigravity
Delegate analytical, sandboxed, or long-running work to the Google Antigravity (agy) CLI via a JSON-bridge wrapper. Use when you need a second opinion, sandboxed execution, or a detached long-running agent loop. Install location is .agents/skills/collaborating-with-antigravity/.
review-security
Review code changes with Security Review subagent.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
gemini-cli-runtime
Internal helper contract for calling the gemini-companion runtime from Claude Code.