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/entireio/cli/agent-integrationnpx skills add entireio/cli --skill agent-integrationgit clone --depth 1 https://github.com/entireio/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.00089 | $0.01370 |
| Opus 5 | $0.00044 | $0.00685 |
| Sonnet 5 | $0.00018 | $0.00274 |
| Haiku 4.5 | $0.00009 | $0.00137 |
Grade A, and why
agent-integration 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 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.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Integration — Full Pipeline
Run all three phases of agent integration in a single session. Parameters are collected once and reused across all phases.
Parameters
Collect these before starting (ask the user if not provided):
| Parameter | Description | How to derive |
|---|---|---|
AGENT_NAME |
Human-readable name (e.g., "Gemini CLI") | User provides |
AGENT_PACKAGE |
Go package dir name — no hyphens | Lowercase, remove hyphens/spaces |
AGENT_KEY |
Registry key for agent.Register() and entire enable |
Check existing patterns in cmd/entire/cli/agent/registry.go |
AGENT_SLUG |
Filesystem/URL-safe slug (kebab-case) used in E2E runner filenames and script names | Kebab-case of agent name; align with existing entries in e2e/agents/ |
AGENT_BIN |
CLI binary name | command -v <binary> |
LIVE_COMMAND |
Full command to launch agent | User provides |
EVENTS_OR_UNKNOWN |
Known hook event names, or "unknown" | From agent docs or "unknown" |
Note: These identifiers can differ. Run grep -r 'AgentName\|func.*Name()' cmd/entire/cli/agent/*/ and e2e/agents/ to see how existing agents handle the split.
Architecture References
These documents define the agent integration contract:
- Implementation guide:
docs/architecture/agent-guide.md— Step-by-step code templates, event mapping, testing patterns - Integration checklist:
docs/architecture/agent-integration-checklist.md— Design principles and validation criteria
Scope
This skill targets hook-capable agents — those that support lifecycle hooks
(implementing HookSupport from agent.go). Agents that use file-based detection
(implementing FileWatcher) require a different integration approach not covered here.
Check agent.go for the current interface definitions.
Core Rule: E2E-First TDD
This skill enforces strict E2E-first test-driven development. The rules:
- E2E tests are the spec. The existing
ForEachAgenttest scenarios define what "working" means. The agent runner makes those tests runnable for the new agent. - Run E2E tests at every step. Each implementation tier starts by running the E2E test and watching it fail. You implement until it passes. No exceptions.
- Unit tests are written last. After all E2E tiers pass (Step 14), you write unit tests using real data collected from E2E runs as golden fixtures.
- If you didn't watch it fail, you don't know if it tests the right thing. Never write a test you haven't seen fail first.
- Minimum viable fix. At each E2E failure, implement only the code needed to fix that failure. Don't anticipate future tiers.
/e2e:debugis your debugger. When an E2E test fails, use the artifact directory with/e2e:debugbefore guessing at fixes.
What ships with it
4 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 · 108 lines · 89 tokens per session scan A 02520fdc47e5
agent-integration is a skill published in the GitHub repository entireio/cli (5,045 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 1,370 once invoked, about $0.0004 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-30.
Other skills, from other repositories
google-agents-cli-deploy
This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud Run, or GKE deployment targets, or binding an agent to an Agent Gateway. Covers deployment workflows, service accounts…
google-agents-cli-eval
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Agent Platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset…
google-agents-cli-workflow
This skill should be used when the user wants to "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "deploy an agent", "publish an agent", "monitor an agent", or needs the ADK (Agent Development Kit) development lifecycle and coding guidelines. Entrypoint for…
google-agents-cli-observability
This skill should be used when the user wants to "set up tracing", "monitor my agent", "configure logging", "add observability", "debug production traffic", or needs guidance on monitoring deployed agents, including ADK (Agent Development Kit) agents. Covers Cloud Trace, prompt-response logging, BigQuery Agent…
google-agents-cli-publish
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the agents-cli publish gemini-enterprise command. Also use when the user wants to "manage agents in Agent Registry"…
google-agents-cli-scaffold
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers agents-cli scaffold create, scaffold enhance, and…