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/jpantsjoha/googlecloud-plugin/agents-mdgit clone --depth 1 https://github.com/jpantsjoha/googlecloud-pluginWhat 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.00426 | $0.00426 |
| Opus 5 | $0.00213 | $0.00213 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
googlecloud-plugin 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 yesterday.
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
AGENTS.md — GoogleCloud Plugin (Codex always-on adapter)
Human-led. Agent-powered. Built on Google Cloud.
Codex discovers this plugin's skills under .agents/skills/ and reads this file as the always-on contract for Google Cloud work. The skills carry the depth; this file carries the rules.
Design before generate
Restate the intent in one sentence before writing code. No GCP implementation without a design — route through the gate.
The gate (sequential — do not skip)
- Solution Gate —
solution-designer: objective vendor selection (GCP vs alternatives). Skip only if unambiguously GCP-only. - GCP Design Gate —
gcp-architect(+agent-architectfor agentic work): HLD/LLD + ADRs before code. - Security Gate —
gcp-security: least-privilege IAM, no secrets, Well-Architected security. Reviews the design. - Implementation — service skills; warn before every billable action.
- Quality Gate —
gcp-qarunsmake gate;agent-architectruns agent-eval for agentic work. - Operational Readiness Gate —
gcp-ops: SLO + alerting + runbook before production.
Non-negotiable safety rules
- Infer intent, never infer permission. A named human authorises anything consequential, billable, or irreversible.
- No credential values in any file — record location only.
- No public buckets or unauthenticated Cloud Run without gcp-security sign-off.
- Never pin a preview Gemini model ID; use GA IDs, reverify for the GEAP surface.
- GEAP naming in prose; legacy
vertex-ailiterals in code/URLs/Terraform.
Routing
See PLUGIN.md for the full routing table. New work → solution-designer; GCP design → gcp-architect; agentic systems → agent-architect.
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.
- yesterday First seen · 31 lines · 426 tokens per session scan A 426b078d108e
googlecloud-plugin AGENTS.md is an instructions file published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 25d ago), licensed MIT. It adds 426 tokens to every session, about $0.0021 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
debroid AGENTS.md
Instructions for PatilShreyas/debroid, covering ai agent contributor guide 🤖, 🎯 intention & motivation, 🏗️ architecture & layers, 1. the core layer (jdi & adb orchestration) and 2. the cli layer (daemon & client).
AgentHound copilot-instructions.md
Instructions for adithyan-ak/AgentHound: Keep generated examples local to the fixture project.
a2a-editor CLAUDE.md
Instructions for open-resource-discovery/a2a-editor, covering claude.md, project overview, commands, development and building.
agent-ship CLAUDE.md
Instructions for Agent-Ship/agent-ship, covering claude.md, project overview, commands, docker development (recommended) and local development (no docker).
adk AGENTS.md
Instructions for inference-gateway/adk, covering inference gateway a2a adk, project overview, build, test, and development commands, generated files and code style.
ampersend-sdk CLAUDE.md
Instructions for edgeandnode/ampersend-sdk, covering claude.md, project overview, development commands, python setup and install python 3.13.