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 skills add Vit129/agy-plugin-cc --skill agy-result-handlinggit clone --depth 1 https://github.com/Vit129/agy-plugin-ccWrote 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/skills/vit129/agy-plugin-cc/agy-result-handling)<a href="https://agentmods.dev/skills/vit129/agy-plugin-cc/agy-result-handling"><img src="https://agentmods.dev/badge/skills/vit129/agy-plugin-cc/agy-result-handling.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.1 | $0.00016 | $0.00317 |
| Opus 5 | $0.00008 | $0.00159 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
agy-result-handling 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
agy Result Handling
When the helper returns agy output:
- Preserve the helper's findings and next steps structure.
- For review output, present findings first, ordered by severity if provided.
- Use the file paths and line numbers exactly as agy reports them.
- Preserve evidence boundaries. If agy marked something as an inference or uncertainty, keep that distinction.
- If there are no findings, say that explicitly and keep the residual-risk note brief.
- If agy made edits, say so explicitly and list the touched files when the helper provides them.
- For
agy:agy-rescue, do not turn a failed or incomplete agy run into a Claude-side implementation attempt. Report the failure and stop. - For
agy:agy-rescue, if agy was never successfully invoked, do not generate a substitute answer at all. - CRITICAL: After presenting review findings, STOP. Do not make any code changes. Do not fix any issues. You MUST explicitly ask the user which issues, if any, they want fixed before touching a single file. Auto-applying fixes from a review is strictly forbidden, even if the fix is obvious.
- If the helper reports a failed agy run, include the most actionable error lines and stop there instead of guessing.
- If the helper reports that setup is required, direct the user to
/agy:setupand do not improvise alternate flows.
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 · 21 lines · 16 tokens per session scan A ece257e2a165
agy-result-handling is a skill published in the GitHub repository Vit129/agy-plugin-cc (5 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 317 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.
antigravity-result-handling
How to interpret Antigravity companion output — successful responses, quota/auth/backend errors, and applying file changes.
gemini-3-prompting
How to write effective prompts for Google Antigravity / Gemini 3.5 agents (used when delegating to or reviewing with the antigravity plugin).
antigravity-cli-runtime
Internal helper contract for calling the antigravity companion runtime from Claude Code.
agy-researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /skill:agy-researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.
researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy:researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.