agents-cli
The CLI and skills that turn any coding assistant into an expert at creating, evaluating, and deploying AI agents on Google Cloud.
Runs with mockssource: GitHubhomepagePythonApache-2.0commit 5597738f14b5
Python, Apache-2.0 licensed. The project labels itself: adk, agent development kit, agents, coding agent, gemini, gemini enterprise agent platform, generative ai and google cloud.
agents-cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 10 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
google-agents-cli v1.5.0 installed and verified: CLI displays help, creates projects, installs deps, shows info; all 47 langchain extension tests pass; project unit tests pass; integration tests correctly report missing API keys (expected without real credentials).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 86 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 10 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- Model tokens used
- 62,723
- Exact commit tested
- 5597738f14b5
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
# and checking from a fresh shell export PATH="/tmp/venv/bin:$PATH" && google-agents-cli --version 2>&1' in /work/repo succeeded in 32ms: exec /bin/sh -lc '# calc time: started ~18:46, now ~18:56 echo "Approx runtime: ~10 minutes"' in /work/repo succeeded in 0ms: Approx runtime: ~10 minutes Let me compile everything and produce the final report: tokens used 62,723 Let me compile everything and produce the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 10 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.06 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.05 |
Topics (from GitHub)
adkagent-development-kitagentscoding-agentgeminigemini-enterprise-agent-platformgenerative-aigoogle-cloud
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/agents-cli)Questions
- Does agents-cli run?
- agents-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 10 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test agents-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5597738f14b5. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test agents-cli?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does agents-cli take to install?
- 10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does agents-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing agents-cli?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for agents-cli?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.