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 instructions/gradio-app/gradio/agents-mdgit clone --depth 1 https://github.com/gradio-app/gradioWrote 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/gradio-app/gradio/agents-md)<a href="https://agentmods.dev/instructions/gradio-app/gradio/agents-md"><img src="https://agentmods.dev/badge/instructions/gradio-app/gradio/agents-md.svg" alt="Measured on agentmods" 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 | $0.00821 | $0.00821 |
| Opus 5 | $0.00411 | $0.00411 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
gradio 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents working on this repository.
Repository Structure
gradio/— Python source for the Gradio library (backend)gradio/components/— all Gradio componentsgradio/cli/— CLI commands (gradio,gradio cc,gradio skills, etc.)
client/python/— thegradio_clientPython client libraryclient/js/— the@gradio/clientJavaScript client libraryjs/— frontend code (Svelte/TypeScript), with each component in its own subdirectorytest/— Python backend tests (pytest)js/spa/test/— browser/Playwright tests (*.spec.ts)demo/— example Gradio appsguides/— written guides and tutorials for the website
Pull Request Rules
Follow these rules when creating or contributing to pull requests:
-
Target an issue. Every non-trivial PR should reference an existing GitHub issue. If one doesn't exist, create it first. PRs without a linked issue may be closed.
-
Use the PR template. Fill out every section of
.github/PULL_REQUEST_TEMPLATE.md, including:- A clear description of the change
- The AI disclosure checkbox (see below)
- The linked issue (
Closes: #NNN)
-
AI disclosure is mandatory. If AI was used in any non-trivial way (drafting code, writing the PR description, etc.), you must disclose this in the PR template. Trivial autocomplete does not need to be disclosed. All AI-generated code must be self-reviewed.
-
Format your code before pushing.
- Backend:
bash scripts/format_backend.sh - Frontend:
bash scripts/format_frontend.sh
- Backend:
-
Tests must pass. PRs are only merged when CI is green. Run backend tests locally with
bash scripts/run_backend_tests.sh. -
PR title and description should be clear and written in English. The title should concisely describe what the PR does. The description should explain why.
-
Don't write changeset files. A GitHub Action adds
.changeset/*.mdto your branch from the PR title, so a good title is all that's needed. The bot leaves an existing changeset alone, so a hand-written one silently replaces your title in the changelog.
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.
- 4d ago First seen · 73 lines · 821 tokens per session scan A 975541e72c77
gradio AGENTS.md is an instructions file published in the GitHub repository gradio-app/gradio (43,451 stars, last pushed 2d ago), licensed Apache-2.0. It adds 821 tokens to every session, about $0.0041 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 instructions, from other repositories
tamagui AGENTS.md
AGENTS.md instructions for tamagui/tamagui, covering tamagui — agent operating contract, finish what you start, then merge it back, tamagui testing guide, running tests and kitchen sink tests.
huggingface_hub AGENTS.md
AGENTS.md instructions for huggingface/huggingface_hub, covering agent guide for huggingfacehub, project overview, setup, key commands and code structure.
ui-components AGENTS.md
AGENTS.md instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).
unity-ui-toolkit-design-system AGENTS.md
Instructions for sinanata/unity-ui-toolkit-design-system, covering agents.md, what this project is, golden rules (do not violate), use the design system in your project and repository layout.
web-interface-guidelines AGENTS.md
Instructions for vercel-labs/web-interface-guidelines, covering interactions, keyboard, targets & input, forms and state & navigation.
unity-ui-toolkit-design-system copilot-instructions.md
Instructions for sinanata/unity-ui-toolkit-design-system: This repository follows the cross-tool AGENTS.md standard. Read /AGENTS.md for the full guide: the ds- class naming, the token rules, the load-bearing USS import order, build and preview commands, and the pull-request checklist.