agents-cli is a command-line tool and collection of skills that guides coding assistants through building, evaluating, and deploying AI agents on Google's Gemini Enterprise Agent Platform. Developers use it with assistants such as Claude Code, Codex, and Antigravity CLI to work with Google Cloud agent services. The catalogue entries provide skills and a plugin for that development workflow.
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 skills add google/agents-cli --skill google-agents-cli-workflowgit clone --depth 1 https://github.com/google/agents-cliWrote 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/skills/google/agents-cli/google-agents-cli-workflow)<a href="https://agentmods.dev/skills/google/agents-cli/google-agents-cli-workflow"><img src="https://agentmods.dev/badge/skills/google/agents-cli/google-agents-cli-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/google/agents-cli/google-agents-cli-workflow"><img src="https://agentmods.dev/badge/skills/google/agents-cli/google-agents-cli-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 325 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium MCP Rug Pull · line 24 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 37 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium Tool Misuse · line 325 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00126 | $0.05076 |
| Opus 5.5 | $0.00050 | $0.02030 |
| Sonnet 5.5 | $0.00025 | $0.01015 |
| Haiku 4.5 | $0.00013 | $0.00508 |
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 3d 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 Copies of this mod
1 near-identical copy found in the catalogue:
- google-agents-cli-workflow — 100% identical, 42 lines differ
How it starts
The opening of the file, as written. The whole thing — 339 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.10.0 If version is behind, run: uv tool install "google-agents-cli=1.10.0"
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, before scaffolding. Python: the references/samples.md topic index maps a need to the recipe that implements it. Go: the upstream examples/ are the equivalent. Yes, load this early. |
| 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 (optional) |
| 7 — Observe | /google-agents-cli-observability |
After deploying — traces, logging, monitoring setup |
What ships with it
6 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.
- 3d ago Changed · +1 lines 849864a49e6b
- 9d ago Changed b99ae4852131
- 15d ago Changed f6a0eb6d0012
- 23d ago Changed · +1 lines bf5a95932ca3
- 29d ago Changed · +8 lines e1f44af61d22
- 1mo ago Changed · +3 lines 3f7af2536bd7
- 1mo 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 (6,094 stars, last pushed 4d ago), licensed Apache-2.0. It adds 126 tokens to every session and 5,076 once invoked, about $0.0005 per session on Opus 5.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.
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, resolve/search/record, graph workbench reads/writes, and pot scope behavior.
potpie-change-timeline
Use when an agent needs recent or historical change context: what changed recently, regressions, merged PRs, tickets, docs, incidents, deployments, releases, and source-history ingestion.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.