Borrowing it
Nothing to install: this file belongs to ai-4-you/chrome-tab-remote. 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/ai-4-you/chrome-tab-remote/main/AGENTS.mdgit clone --depth 1 https://github.com/ai-4-you/chrome-tab-remoteWrote 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/ai-4-you/chrome-tab-remote/agents-md)<a href="https://agentmods.dev/instructions/ai-4-you/chrome-tab-remote/agents-md"><img src="https://agentmods.dev/badge/instructions/ai-4-you/chrome-tab-remote/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.01006 | $0.01006 |
| Opus 5 | $0.00503 | $0.00503 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
chrome-tab-remote 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 5d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — chrome-tab-remote
Durable collaboration memory for this repository. Read PROJECT_OVERVIEW.md first for current state and next actions.
What this repo is
A trust-first Chrome extension (plus backend communication) that lets a user explicitly select one tab which a backend/agentic system may then inspect and control. Security and corporate adoptability are the product's core differentiator, not an afterthought. North star: IDEA.md.
Collaboration rules (durable)
- 2026-08-02: Git commits must NOT carry a
Co-Authored-By: Claude …trailer (user decision; overrides the default).
Scope decisions (durable)
- 2026-08-04: Distribution for v1 is a public Chrome Web Store listing. Managed enterprise force-install by Store ID remains compatible; enterprise certification and signed/cross-platform native-host productisation are a separate delivery track. Canonical execution plan:
docs/cws-signed-publishing-plan.md. - 2026-08-04: Viewport screenshots are permitted only through a separate, default-off
Allow ViewportScreenshotgrant capability. It is limited to the granted tab’s already-active visible viewport; it never focuses, scrolls, persists images, or grants full-page capture. Its normal origin pin, session expiry, revocation, call-time validation, and audit all apply. - 2026-08-02: Focus is the Chrome extension and its communication with a backend system only. The knowledge-gathering/RAG side of the reference system chrome-tracker is explicitly out of scope.
- The extension is purpose-built for interactive tab control — no tracking/knowledge-base machinery bundled in.
Design principles
- Agent-facing output is prose-shaped: the consumer of MCP tool results is a language model, so compact readable text is the machine format. JSON only earns its place when something programmatic re-reads the result — and then as MCP
structuredContentalongside the text, never instead of it. Errors follow the same rule: every error carries a concrete "Next step:" recovery instruction, not just a diagnosis.
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.
- 5d ago First seen · 56 lines · 1,006 tokens per session scan A 17d7dc8fe081
chrome-tab-remote AGENTS.md is an instructions file published in the GitHub repository ai-4-you/chrome-tab-remote (0 stars, last pushed 11d ago), licensed MIT. It adds 1,006 tokens to every session, about $0.0050 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
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.
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).
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).
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.
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.