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/adk-docs/integration-reviewnpx skills add google/adk-docs --skill integration-reviewgit clone --depth 1 https://github.com/google/adk-docsWhat 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.00110 | $0.06035 |
| Opus 5 | $0.00055 | $0.03018 |
| Sonnet 5 | $0.00022 | $0.01207 |
| Haiku 4.5 | $0.00011 | $0.00604 |
Grade A, and why
integration-review 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 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.
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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADK Integration Page Reviewer (integration-review)
This skill guides a rigorous review of integration documentation pages in the
adk-docs repository. Integration pages
live under docs/integrations/ and document third-party tools, plugins,
observability platforms, data stores, MCP servers, connectors, and other
extensions to ADK agents.
The authoritative sources of truth for this review are:
- The repository's
CONTRIBUTING.md(see the "Integrations" section and its acceptance criteria). - The existing shipping integration pages, which are the real template.
Always open and compare against peers of the same category:
- MCP tools:
docs/integrations/github.md,docs/integrations/notion.md - Observability:
docs/integrations/phoenix.md,docs/integrations/arize-ax.md - Plugins:
docs/integrations/daytona.md,docs/integrations/goodmem.md
- MCP tools:
- The catalog rendering logic in
scripts/integrations.py.
[!NOTE] Read this skill and follow its steps whenever asked to review an integration page or an integration PR.
Review workflow
Step 1: Gather the change
- If reviewing a PR, use
ghto pull it and read the full cumulative diff, not a single commit:gh pr view <n> --repo google/adk-docsandgh pr diff <n> --repo google/adk-docs. A stalemkdocs.ymlentry or asset can hide in files that only show in the full diff. - Check whether "Allow edits from maintainers" is enabled
(
maintainerCanModify) so fixes can be pushed directly if requested later. - Confirm the CLA is signed (the
google-clabot). An unsigned CLA is a 🔴 Critical finding and blocks merge until signed. - If reviewing a local file, run
git statusandgit diffto see the change.
Step 2: Find and read similar pages
Find 5 or more similar pages and read them in full. Identify candidates in one
pass by scanning catalog_tags (grep catalog_tags docs/integrations/*.md) and
matching the tag under review (e.g. mcp, observability); widen the set with
other signals such as product domain, structural template, and language support
(they need not all be the exact same category). Reading the full pages, not just
frontmatter, grounds the review in live examples and repo conventions rather
than inferring everything from the templates in this skill.
What ships with it
1 file 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 First seen · 468 lines · 110 tokens per session scan A 686587329407
integration-review is a skill published in the GitHub repository google/adk-docs (1,479 stars, last pushed 5d ago), licensed Apache-2.0. It adds 110 tokens to every session and 6,035 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…