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 skills/google/agents-cli/google-agents-cli-workflownpx skills add google/agents-cli --skill google-agents-cli-workflowgit clone --depth 1 https://github.com/google/agents-cliWhat 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.00126 | $0.04751 |
| Opus 5 | $0.00063 | $0.02375 |
| Sonnet 5 | $0.00025 | $0.00950 |
| Haiku 4.5 | $0.00013 | $0.00475 |
Grade A, and why
google-agents-cli-workflow scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Use WebFetch on URLs from the ADK docs index (`curl https://adk.dev/llms.txt`) for deep dives How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Development Workflow & Guidelines
agents-cli is a CLI and skills toolkit for building, evaluating, and deploying agents on Google Cloud. It works with any coding agent — Antigravity CLI, Claude Code, Codex, or others — and with the agent framework of your choice (the Agent Development Kit (ADK) by default). Install with uvx google-agents-cli setup.
Before writing agent code, make sure a scaffolded project exists (see Phase 2). Skipping scaffolding loses eval boilerplate, CI/CD config, and project conventions.
Requires: google-agents-cli
= 1.4.2 If version is behind, run: uv tool install "google-agents-cli=1.4.2"
Check version: agents-cli info Install uv first if needed.
Session Continuity & Skill Cross-References
Re-read the relevant skill before each phase — not after you've already started and hit a problem. Context compaction may have dropped earlier skill content. If skills are not available, run uvx google-agents-cli setup to install them.
| Phase | Skill | When to load |
|---|---|---|
| 0 — Understand | — | No skill needed — read .agents-cli-spec.md if present, else clarify goals with the user |
| 1 — Study recipes | /google-agents-cli-adk-code |
Load it during design — its references/samples.md topic index maps a need to the recipe that implements it. Yes, this early: the catalog lives there. |
| 2 — Scaffold | /google-agents-cli-scaffold |
Before creating or enhancing a project |
| 3 — Build | /google-agents-cli-adk-code |
Before writing agent code — API patterns, tools, callbacks, state |
| 4 — Evaluate | /google-agents-cli-eval |
Before running any eval — dataset schema, metrics, eval-fix loop |
| 5 — Deploy | /google-agents-cli-deploy |
Before deploying — target selection, troubleshooting 403/timeouts |
| 6 — Publish | /google-agents-cli-publish |
After deploying, if registering with Gemini Enterprise (optional) |
| 7 — Observe | /google-agents-cli-observability |
After deploying — traces, logging, monitoring setup |
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.
- 2d ago First seen · 326 lines · 126 tokens per session scan A 53bf828a711c
google-agents-cli-workflow is a skill published in the GitHub repository google/agents-cli (5,759 stars, last pushed 4d ago), licensed Apache-2.0. It adds 126 tokens to every session and 4,751 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
adk-student-evaluator
Acts as a student developer to evaluate ADK training modules. Follows a rigorous 5-step workflow to test labs and generate formal pedagogical reports. Use when asked to "evaluate", "test as a student", or "review" a training module.
adk-skill
Use this skill for developing agents using the Google Agent Development Kit (ADK) in Python. Provides guidelines, best practices, and documentation.
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
test-repo
Use this skill to test strategy changes against a fresh test repository. Invoke when the user asks to "test against a test repo", "validate the changes", or wants to verify session hooks, commits, and rewind functionality work correctly.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
grocery-prices
A skill to calculate grocery prices with country-specific taxes.