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 PyModel/claude-agy-mcp --skill agy-delegategit clone --depth 1 https://github.com/PyModel/claude-agy-mcpWrote 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/pymodel/claude-agy-mcp/agy-delegate)<a href="https://agentmods.dev/skills/pymodel/claude-agy-mcp/agy-delegate"><img src="https://agentmods.dev/badge/skills/pymodel/claude-agy-mcp/agy-delegate/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/skills/pymodel/claude-agy-mcp/agy-delegate"><img src="https://agentmods.dev/badge/skills/pymodel/claude-agy-mcp/agy-delegate.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.00132 | $0.03202 |
| Opus 5 | $0.00066 | $0.01601 |
| Sonnet 5 | $0.00026 | $0.00640 |
| Haiku 4.5 | $0.00013 | $0.00320 |
Grade A, and why
agy-delegate 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 today.
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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity Delegate
You are the orchestrator. This skill lets you hand a bounded coding task to a separate
implementer - the Google Antigravity CLI (agy) - then review what it produced and land it
yourself. You write the brief and own the judgment; Antigravity does the typing in its own
conversation; you verify and commit.
There are two dispatch paths and the loop around them is identical:
- MCP (preferred) - the
claude-agy-mcpbridge exposesdelegate,follow_up,adversarial_review,delegate_manyand friends as tools. Use this whenever the tools are available. - CLI relay (fallback) -
scripts/relay.mjswrapsagy --printand writes aresult.json. Use it when the MCP server is not registered, so an orchestrator that can only run a shell command and read a file can still drive the loop.
When NOT to use this
- The task is small enough to just do inline - delegation overhead is not worth it.
- Neither the MCP server nor the
agyCLI is available and authenticated. - You want to write the code yourself, or you only need Antigravity's opinion on code you wrote - a
read-only
delegateoradversarial_reviewcovers that, but a plain review may not need delegation at all.
Prerequisites (check once)
-
Load the tools. In an orchestrator where the bridge's tools are deferred, load them in a single call, not one per tool:
ToolSearch("select:mcp__claude-agy-mcp__delegate,mcp__claude-agy-mcp__follow_up,mcp__claude-agy-mcp__adversarial_review,mcp__claude-agy-mcp__delegate_many,mcp__claude-agy-mcp__agy_status,mcp__claude-agy-mcp__set_model") -
Call
agy_status. It never reaches agy, so it is a free liveness check. It reports the agy version, the models on offer, the resolved model chain per tool, quota cooldowns, in-flight runs, and whether aset_modelchoice has already been recorded. -
Settle the model once, if
agy_statusshows no choice recorded. The bridge defaults toAGY_ASK_MODEL=trueand refuses to delegate untilset_modelhas been called - the first delegation returns an error, not a result. Ask the user "proceed with the default, or change model or effort?", then callset_modelonce: no arguments accepts the default (Gemini Flash High), or pass what they chose. The choice is saved per machine and no tool asks again. An explicitmodelon a single call still wins for that call.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 220 lines · 132 tokens per session scan A 7952327c5f93
agy-delegate is a skill published in the GitHub repository PyModel/claude-agy-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 132 tokens to every session and 3,202 once invoked, about $0.0007 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-09-14.
Other skills, from other repositories
quality-playbook
Explore any codebase from scratch and generate six quality artifacts: a quality constitution (QUALITY.md), spec-traced functional tests, a code review protocol with regression test generation, an integration testing protocol, a multi-model spec audit (Council of Three), and an AI bootstrap file (AGENTS.md). Includes…
architecture-review
Use when you need to evaluate architecture, coupling, duplication, integration fit, and whether to keep, adapt, or replace existing structures.
python-anti-patterns
Use this skill when reviewing Python code for common anti-patterns to avoid. Use as a checklist when reviewing code, before finalizing implementations, or when debugging issues that might stem from known bad practices.
python-code-style
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
gamedev-code-review
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
diff-review
Use when reviewing a code change before committing — e.g. the user says "review my diff", "karpathy check", "am I overcomplicating this", "check complexity before I commit", or when finalizing AI-generated code. Audits the staged diff against four principles (surface assumptions, keep it simple, surgical changes…