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 instructions/pymodel/claude-agy-mcp/claude-mdgit 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/instructions/pymodel/claude-agy-mcp/claude-md)<a href="https://agentmods.dev/instructions/pymodel/claude-agy-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pymodel/claude-agy-mcp/claude-md.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.00221 | $0.00221 |
| Opus 5 | $0.00111 | $0.00111 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
claude-agy-mcp CLAUDE.md 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 5d 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.
This is a copy
89% identical to agy-bridge CLAUDE.md — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Delegation rules: claude-agy-mcp
You have claude-agy-mcp MCP tools that delegate heavy work to the Antigravity CLI (Gemini). Delegation keeps large content OUT of your context — only answers come back. Prefer delegating over doing it yourself when:
- Any file >200 lines you'd otherwise read →
analyze_files - More than 3 files in one analysis/comparison →
analyze_files - Git history or repo-wide searches (git log/diff/blame, broad greps) →
deep_search - Web/documentation lookups →
web_lookup - Plan critique or code review →
adversarial_review(always — a second model family catches what you miss) - Follow-up question on a prior delegation →
follow_upwith the returned session id (never resend the context)
Do NOT delegate: small single-file edits, questions you can answer from context already loaded, or tasks needing tools only you have.
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.
- 5d ago First seen · 18 lines · 221 tokens per session scan A 117b9924de8e
claude-agy-mcp CLAUDE.md is an instructions file published in the GitHub repository PyModel/claude-agy-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 221 tokens to every session, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to agy-bridge CLAUDE.md, differing in 4 lines, and is treated as a copy.
Other instructions, from other repositories
agy-plugin-cc CLAUDE.md
Instructions for Vit129/agy-plugin-cc, covering agy-plugin-cc — claude code guide, agent memory, global-first rule, project context (auto-loaded every session) and project summary.
ag-sdd AGENTS.md
AGENTS.md instructions for stormlive-ai/ag-sdd, covering agents.md — anti-gravity spec-driven development (ag-sdd), 1. purpose & philosophy, 2. sdd workflow lifecycle, phase 1 — discovery (mandatory clarification gate) and phase 2 — spec generation.
antigravity-cli-mcp AGENTS.md
AGENTS.md instructions for nadimtuhin/antigravity-cli-mcp, covering mcp tools: code-review-graph, when to use graph tools first, key tools and workflow.
antigravity-cli-mcp CLAUDE.md
Claude Code instructions for nadimtuhin/antigravity-cli-mcp, covering mcp tools: code-review-graph, when to use graph tools first, key tools and workflow.
antigravity-cli-mcp GEMINI.md
Gemini CLI instructions for nadimtuhin/antigravity-cli-mcp, covering mcp tools: code-review-graph, when to use graph tools first, key tools and workflow.
toh-framework CLAUDE.md
Claude Code instructions for wasintoh/toh-framework, covering claude.md — toh framework (repo development guide), what this is, everyday commands, verification protocol and single source, transformed per ide.