adk-go AGENTS.md

Repository instructions for developers and coding agents working on Google’s ADK Go, a Go toolkit for building AI agents. They describe the project, setup commands, repository layout, and completion criteria.

In plain words
What is it for?
Setting up the ADK Go repository, choosing the right branch and commands, and verifying changes across its Go modules.
Why use it?
They give an unfamiliar contributor the project context and the checks needed before considering a change finished.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/google/adk-go/agents-md
Clone the repo
git clone --depth 1 https://github.com/google/adk-go

Made for: Codex, OpenCode.

Per session 2,451 This file is loaded in full into every session.
When invoked 2,451 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02451 $0.02451
Opus 5 $0.01226 $0.01226
Sonnet 5 $0.00490 $0.00490
Haiku 4.5 $0.00245 $0.00245

Measured today against content hash c273def058d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

adk-go AGENTS.md 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 today.

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.

AGENTS.md · 206 lines

How it starts

The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Context for AI coding agents (Claude Code, Gemini CLI, Cursor, Copilot, etc.) working in the ADK Go repository. Human contributors should start with CONTRIBUTING.md.

Project overview

ADK Go (google.golang.org/adk/v2) is an open-source, code-first Go toolkit for building, evaluating, and deploying AI agents. It is model-agnostic but optimized for Gemini, and is one of several ADK implementations — Go, Python, Java, Kotlin, and TypeScript — that share a conceptual model but are independent codebases. Requires the Go version declared in go.mod (currently 1.26.5).

Development happens on main, the 2.x line. v1 is the maintenance branch for 1.x; target it only for fixes that must ship to 1.x. See Branches.

Skills

See AI-assisted development in CONTRIBUTING.md for what this repo ships. The rule for agents: task-specific instructions live in .agents/skills/<name>/SKILL.md, and you read the matching one before starting that kind of work.

Setup & core commands

This repo is multi-module: the root module google.golang.org/adk/v2 plus plugin/agentanalytics. Set up a Go workspace first — go.work is local-only and gitignored, and go work init fails if one already exists:

test -f go.work || go work init
go work use -r .

Then run from the repo root. The work pattern spans every module in the workspace, while ./... matches only the module you are standing in:

  • Build: go build -mod=readonly work
  • Test: go test -race -mod=readonly -count=1 -shuffle=on work
  • Single pkg: go test -race ./agent/...
  • Lint: golangci-lint run (per module; v2, CI pins v2.3.1; config in .golangci.yml)
  • Tidy check: go mod tidy -diff (per module; must print nothing)
  • Format: golangci-lint fmt (per module; applies gofumpt + goimports per config)

Without a go.work, work silently falls back to the root module alone and still exits 0, so confirm the workspace exists before trusting a green run. golangci-lint and go mod tidy are per-module either way: run them inside each submodule too (for example, cd plugin/agentanalytics). CI does the same, running build, test, tidy, and lint once per module, with -v on build and test.

Read the full file on GitHub · 206 lines

Changes

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.

  1. today Changed · +7 lines · +70 tokens per session c273def058d2
  2. 2d ago First seen · 199 lines · 2,381 tokens per session scan A 2bc2a462bd5b

Subscribe to this mod's changes

adk-go AGENTS.md is an instructions file published in the GitHub repository google/adk-go (8,736 stars, last pushed today), licensed Apache-2.0. It adds 2,451 tokens to every session, about $0.0123 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.