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/ykdojo/antigravity-cloud-run/agents-mdgit clone --depth 1 https://github.com/ykdojo/antigravity-cloud-runWrote 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/ykdojo/antigravity-cloud-run/agents-md)<a href="https://agentmods.dev/instructions/ykdojo/antigravity-cloud-run/agents-md"><img src="https://agentmods.dev/badge/instructions/ykdojo/antigravity-cloud-run/agents-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 | $0.00942 | $0.00942 |
| Opus 5 | $0.00471 | $0.00471 |
| Sonnet 5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
antigravity-cloud-run AGENTS.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 4d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity on Cloud Run
Sandboxed Docker container running the Antigravity CLI (agy), accessible via a web terminal.
See architecture.md for full design details.
Testing end to end
After making changes, rebuild and test:
./scripts/build.sh
./scripts/run.sh
This opens http://localhost:7681 in the browser. Verify:
- agy launches automatically with bypass permissions
- Confirm it doesn't ask for login (after the one-time Google sign-in per session)
- Send a message and confirm it gets a response
Multiple sessions
Run multiple isolated sessions with -s:
./scripts/run.sh -n # default on port 7681
./scripts/run.sh -s work -n # agrun-work on next available port
./scripts/run.sh -s research -n # agrun-research on next available port
Mounting local projects
Use -v to mount a local directory into the container. Keep the same folder name inside the container for clarity:
./scripts/run.sh -s myproject -n -v /path/to/myproject:/home/agrun/myproject
This mounts the project at /home/agrun/myproject inside the container. Use the same folder name (not a generic "project") so it's clear which project you're working with. If the container already exists, it will be recreated with the new mount.
Research sessions
For web research or any task requiring URL fetching, use a container session instead of doing it directly on the host. Start (or reuse) a session, then send the query to agy via tmux (see "Sending commands to the container via tmux" below):
./scripts/run.sh -s research -n
docker exec agrun-research tmux send-keys -t main 'Research Inngest and explain how durable execution works' Enter
Dashboard
Start the dashboard to manage all sessions:
npx nodemon dashboard/server.js
Always use nodemon during development for auto-restart on changes.
Opens at http://localhost:7680. Shows all sessions with:
- Start/stop/delete buttons
- Live iframes of active sessions
- Auto-refreshes via Docker events (SSE)
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.
- 4d ago First seen · 99 lines · 942 tokens per session scan A 998538f245ba
antigravity-cloud-run AGENTS.md is an instructions file published in the GitHub repository ykdojo/antigravity-cloud-run (2 stars, last pushed 1mo ago), licensed MIT. It adds 942 tokens to every session, about $0.0047 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 instructions, from other repositories
appwrite AGENTS.md
AGENTS.md instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
icloud-docker AGENTS.md
Instructions for mandarons/icloud-docker, covering icloud docker, quick reference, commands, architecture overview and key conventions.
selfhost-ai CLAUDE.md
Claude Code instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
ilo CLAUDE.md
Claude Code instructions for metio/ilo, covering claude.md, what ilo is, build & test, architecture and key packages (src/main/java/wtf/metio/ilo/).
imagine-mcp AGENTS.md
AGENTS.md instructions for n24q02m/imagine-mcp, covering imagine-mcp, architecture, tool signatures, model selection and transport modes.
wordpress-nginx-docker-compose CLAUDE.md
Claude Code instructions for urre/wordpress-nginx-docker-compose, covering claude.md, what this is, architecture, two .env files — don't confuse them and common commands.