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 ImL1s/agent-cli-skills --skill agy-cli-agentgit clone --depth 1 https://github.com/ImL1s/agent-cli-skillsWrote 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/iml1s/agent-cli-skills/agy-cli-agent)<a href="https://agentmods.dev/skills/iml1s/agent-cli-skills/agy-cli-agent"><img src="https://agentmods.dev/badge/skills/iml1s/agent-cli-skills/agy-cli-agent/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/iml1s/agent-cli-skills/agy-cli-agent"><img src="https://agentmods.dev/badge/skills/iml1s/agent-cli-skills/agy-cli-agent.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00106 | $0.00852 |
| Opus 5.5 | $0.00042 | $0.00341 |
| Sonnet 5.5 | $0.00021 | $0.00170 |
| Haiku 4.5 | $0.00011 | $0.00085 |
Grade A, and why
agy-cli-agent 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 2mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity CLI (agy) Executor
When to use
- User wants agy / Antigravity as the coding agent
- Orchestrator needs a headless agy run (pipes, CI, council seats)
- Plan-executor / explore helpers (
agy-task.sh,agy-explore.sh)
Prefer other *-cli-agent skills when the user names Claude, Codex, Grok, Kimi, or Qwen.
For multi-provider parallel opinions, use multi-cli-spawn.
Wrapper
# From this skill directory (or after ./install.sh):
./agy-exec.sh -C /path/to/repo -t 900s "Implement the task; stop when done."
./agy-exec.sh -r -C /path/to/repo "Where is auth handled?" # read-only
./agy-exec.sh -T -C /path/to/repo "Large refactor…" # native multi-agent hint
./agy-task.sh -C /path/to/repo -v "npm test" "Do task X"
./agy-explore.sh -C /path/to/repo "How does routing work?"
Shared flags: -m model · -t print-timeout · -C cwd · -f prompt-file · -r read-only ·
-s sandbox · -T teamwork/subagent preamble · --agent · --mode · --effort ·
--add-dir · --no-git · -- passthrough to agy.
Default model: gemini-3.5-flash-high. Discover ids with agy models.
-C is absolutized before use (relative paths are safe).
Critical: PTY required
agy -p prints nothing unless stdout is a real TTY
(gemini-cli#76).
This wrapper always uses lib/pty_run.py. Do not call bare agy -p from pipes/subprocesses.
Native multi-agent
- Interactive:
/teamwork-preview(Ultra plan preview),/agentspanel, custom agents under.agents/agents/ - Headless:
-Tadds a teamwork/subagent preamble; also--agent NAME - We do not reimplement teamwork — we ask agy to use its own orchestration when available
Git hazard
Prompts that mention git show / git diff / git checkout can cause agy to move HEAD.
Prefer pre-computed diffs pasted into the prompt. Use --no-git. Orchestrator owns commits.
Discipline
- Exit code is untrusted — verify with
git diff+ your done-criteria - Prefer disposable git worktrees for autonomous
--dangerously-skip-permissionsruns - One task = one
agy -p(headless resume is unreliable)
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.
- 2mo ago First seen · 67 lines · 106 tokens per session scan A e861ab6c86bc
agy-cli-agent is a skill published in the GitHub repository ImL1s/agent-cli-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 106 tokens to every session and 852 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
agent-desktop
Use the built-in Computer sub-agent with agent-desktop for macOS desktop automation. Apply when a task needs application launching, accessibility snapshots, stable element refs, window focusing, semantic clicks/typing, or visual confirmation outside the browser sandbox.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
financial-analysis
Financial figures done carefully: periods and fiscal calendars, units and currencies, reconciliation, magnitude sanity checks, sourced assumptions. Use for statements, budgets, pricing, and diligence numbers.