agy-bridge
Reduces Claude's context consumption and latency by offloading compute-heavy tasks to specialized CLI tools, enabling longer coding sessions with better toke…
MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, session continuity, and output truncation to save Claude's context and tokens.
- Ask Claude to delegate large file processing tasks to Antigravity CLI without consuming token budget.
- Generate reports using specialized routing to the best available model for each subtask automatically.
- Automate multi-step workflows while maintaining session state across tool boundaries and model switches.
Reduces Claude's context consumption and latency by offloading compute-heavy tasks to specialized CLI tools, enabling longer coding sessions with better token efficiency and fallback resilience.
Engineering teams using Claude Code for complex workflows requiring external tool integration and optimized token spend.
https://github.com/sshahzaiib/agy-bridge
By sshahzaiib
How to Get It
claude plugins install sshahzaiib/agy-bridge
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Delegate large file processing tasks to Antigravity CLI without consuming token budget
Trust Signals Auto-scanned
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 59 GitHub stars; 1 contributors; last commit 34d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 59 GitHub stars; 1 contributors; last commit 34d ago; license MIT.