Borrowing it
Nothing to install: this file belongs to ankit-verma-209171/android-docs-mcp. 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/ankit-verma-209171/android-docs-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/ankit-verma-209171/android-docs-mcpWrote 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/ankit-verma-209171/android-docs-mcp/agents-md)<a href="https://agentmods.dev/instructions/ankit-verma-209171/android-docs-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ankit-verma-209171/android-docs-mcp/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.1 | $0.00486 | $0.00486 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
android-docs-mcp 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 7d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
- This repository contains
android-docs-mcp, a Bun/Node-based MCP server that fetches and parses Android documentation fromdeveloper.android.com. - Runtime entrypoint:
src/index.ts. - Tool implementations live in
src/tools/. - Shared utilities live in
src/lib/.
Working Agreements
- Keep changes focused and minimal; avoid unrelated refactors.
- Preserve the existing ESM TypeScript style and naming patterns already used in
src/. - Prefer small composable helpers in
src/lib/over duplicating logic across tools. - Do not add new dependencies unless clearly necessary.
- Update
README.mdwhen changing tool behavior, configuration, setup, or public usage.
Source Layout
src/index.ts: MCP server registration and bootstrap.src/tools/: public MCP tools. Keep each file centered on one tool.src/lib/cache.ts: cache behavior.src/lib/fetcher.ts: HTTP fetching, retries, and cache integration.src/lib/parser.ts: HTML-to-Markdown conversion.src/lib/url-resolver.ts: Android/API URL resolution..vscode/mcp.json: local MCP client config.
Build And Validation
- Install dependencies with
bun install. - Run local development with
bun run dev. - Build distributable output with
bun run build. - When behavior changes, validate at minimum with
bun run buildbefore finalizing.
Implementation Notes
- Keep tool names, parameter names, and response shapes stable unless the task explicitly requires a breaking change.
- Prefer deterministic parsing and normalization logic; avoid brittle string matching when a structured DOM approach is available.
- Reuse existing fetch/cache/parser utilities before introducing new plumbing.
- Keep network-facing behavior respectful of upstream docs structure and existing retry/caching patterns.
Documentation Expectations
- If you add a new tool, document it in
README.mdwith parameters and usage. - If you change environment variables, update the configuration table in
README.md. - If you change package scripts or startup flow, keep
README.mdand.vscode/mcp.jsonaligned.
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.
- 7d ago First seen · 45 lines · 486 tokens per session scan A 46852d7fb5ea
android-docs-mcp AGENTS.md is an instructions file published in the GitHub repository ankit-verma-209171/android-docs-mcp (9 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 486 tokens to every session, about $0.0024 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.