Borrowing it
Nothing to install: this file belongs to JosephHampton/awesome-gemini-cli-subagents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JosephHampton/awesome-gemini-cli-subagents/main/AGENTS.mdgit clone --depth 1 https://github.com/JosephHampton/awesome-gemini-cli-subagentsWrote 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/instructions/josephhampton/awesome-gemini-cli-subagents/agents-md)<a href="https://agentmods.dev/instructions/josephhampton/awesome-gemini-cli-subagents/agents-md"><img src="https://agentmods.dev/badge/instructions/josephhampton/awesome-gemini-cli-subagents/agents-md/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/instructions/josephhampton/awesome-gemini-cli-subagents/agents-md"><img src="https://agentmods.dev/badge/instructions/josephhampton/awesome-gemini-cli-subagents/agents-md.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.00368 | $0.00368 |
| Opus 5.5 | $0.00147 | $0.00147 |
| Sonnet 5.5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
awesome-gemini-cli-subagents 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.
This is a copy
100% identical to awesome-gemini-cli-subagents GEMINI.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Repository context for coding agents
This repository is Awesome Gemini CLI & Antigravity Subagents: a curated library of subagent definitions for Gemini CLI and Antigravity CLI.
Structure
agents/<category>/<agent-name>.md: the source of truth. One subagent per file, YAML frontmatter plus a system prompt in the body, in Gemini CLI format.antigravity/awesome-subagents/: an Antigravity CLI plugin GENERATED fromagents/byscripts/build-antigravity.sh. Never edit it by hand.README.md: the categorized index of every agent.install-agents.sh: installs the agents for either CLI (--antigravity,--project,--category,--list,--uninstall).scripts/validate.sh: the checks CI runs on every push and pull request.
Conventions when editing here
- Frontmatter fields:
name,description, and optionallykind,tools,model,temperature,max_turns. nameis a unique lowercase-hyphenated slug that matches the filename.- Keep system prompts focused: one clear responsibility per agent, with focus areas, a method, an expected output and explicit guardrails.
- Prompts must stay tool-agnostic (no tool names in the body), because the same body is used by both CLIs.
- Reviewers and auditors do not get
write_file. - Security agents are always framed defensively (audit, detect, harden, remediate).
- After adding, renaming or editing an agent: update its row in
README.md(and the count badge), run./scripts/build-antigravity.sh, then./scripts/validate.sh.
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.
- today First seen · 22 lines · 368 tokens per session scan A c70e1f826027
awesome-gemini-cli-subagents AGENTS.md is an instructions file published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 368 tokens to every session, about $0.0015 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to awesome-gemini-cli-subagents GEMINI.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.