Borrowing it
Nothing to install: this file belongs to mttmcknn/android-emulator-plugin. 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/mttmcknn/android-emulator-plugin/main/AGENTS.mdgit clone --depth 1 https://github.com/mttmcknn/android-emulator-pluginWrote 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/mttmcknn/android-emulator-plugin/agents-md)<a href="https://agentmods.dev/instructions/mttmcknn/android-emulator-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/mttmcknn/android-emulator-plugin/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/mttmcknn/android-emulator-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/mttmcknn/android-emulator-plugin/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.00525 | $0.00525 |
| Opus 5.5 | $0.00210 | $0.00210 |
| Sonnet 5.5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
android-emulator-plugin 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidance for agents
This repository owns the Android emulator plugin. Preserve concurrent user work and inspect the current branch, remote state and applicable instructions before editing. Keep unrelated worktrees and unreleased feature branches out of a release.
Source and generated files
- Edit shared code under
runtime/;plugins/android-emulator-plugin/runtime/is generated bynpm run buildand committed for installation. - The same build copies root screenshots and the authoritative root LICENSE and NOTICE into the installable bundle. Rebuild rather than hand-editing those copies.
- Keep the top-level license and third-party licenses intact. Update the inventory and notices for changes to binaries, downloads, copied code or shipped artwork.
Required changelog and release process
Read GITHUB-RELEASES.md before preparing a version or release. Maintain CHANGELOG.md as part of the change, with a nonempty section matching the plugin/runtime version. Packaging checks this automatically.
- Ground entries in actual commits since the previous release tag. Classify added features, changed behavior, fixes and breaking changes; give migration and new requirements when relevant. Never invent release dates or events.
- Historical development versions must be labelled as development history, not retroactively described as published releases. Use this repository's evidence; importing history from another repository requires substantiated provenance.
- Commit the complete source and generated bundle, then run the documented local packaging command. It builds, runs tests, inspects the ZIP and emits checksums, provenance, review gaps and release notes from the matching changelog section.
- Keep the source commit, existing version tag, ZIP, report and published notes aligned. Inspect licensing and artifact contents before publication. Verify the remote source/tag, downloadable asset bytes and GitHub-visible CI state afterward.
- Build and test locally by default. Do not dispatch Actions or introduce automatic push, PR, tag, release or scheduled CI triggers. Do not change repository settings or credentials to bypass this rule. A manual CI run needs explicit authorization.
- Pushes, tags and releases require the user's request or established authorization; use authorization already supplied in the task. Prepare a reviewable result first. GitHub release publication does not authorize OpenAI Registry submission, policy attestations, new legal agreements or unsupported host compatibility claims.
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 · 44 lines · 525 tokens per session scan A b55ac96376bf
android-emulator-plugin AGENTS.md is an instructions file published in the GitHub repository mttmcknn/android-emulator-plugin (17 stars, last pushed today), licensed Apache-2.0. It adds 525 tokens to every session, about $0.0021 per session on Opus 5.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-10-18.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.