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/imjszhang/js-eyes/agents-mdgit clone --depth 1 https://github.com/imjszhang/js-eyesWrote 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/imjszhang/js-eyes/agents-md)<a href="https://agentmods.dev/instructions/imjszhang/js-eyes/agents-md"><img src="https://agentmods.dev/badge/instructions/imjszhang/js-eyes/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.01954 | $0.01954 |
| Opus 5 | $0.00977 | $0.00977 |
| Sonnet 5 | $0.00391 | $0.00391 |
| Haiku 4.5 | $0.00195 | $0.00195 |
Grade A, and why
js-eyes 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidance for Coding Agents
Project purpose
JS Eyes is a local-first browser capability and site-skill runtime for AI agents. The browser extension, server, SDK, CLI, MCP facade, and optional host adapters are separate layers over the same protocol and policy model.
CLI, MCP, and OpenClaw are peer host surfaces. Do not make a host-specific adapter the owner of behavior that belongs in the host-neutral runtime.
Repository map
apps/clicontains the publicjs-eyescommand.apps/native-hostcontains the browser Native Messaging host.packages/protocolowns shared protocol constants, browser-operation metadata/handlers, and browser-operation catalogs. Install helpers live in@js-eyes/skill-install(not underprotocol).packages/skill-installowns skill discovery, install, trust, ZIP/npm, and registry helpers (formerly underprotocol).packages/policyownsPolicyContextand related egress/taint/task-origin policy primitives used by server-core and the client SDK.packages/client-sdkowns the Node.js browser client (may re-export selected policy symbols from its main entry; prefer@js-eyes/policydirectly).packages/server-coreowns the local HTTP and WebSocket server.packages/mcp-serveris the native stdio MCP facade.packages/skill-contractvalidates Skill metadata;packages/skill-runtimeowns host-neutral Skill Runtime V2, including isolated worker execution.openclaw-plugin(@js-eyes/openclaw-plugin) is an optional OpenClaw adapter workspace. Core packages must not import it.extensions/sharedis the canonical source for cross-browser extension behavior. Chrome and Firefox copies are generated from it.skills/*are independently versioned site skills.packages/devtoolsowns builds, release staging, and generated artifacts.distributioncontains source templates for distributable artifacts.srccontains the public website source.distcontains generated output and must not be edited by hand.
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 · 209 lines · 1,954 tokens per session scan A 7c63823be36c
js-eyes AGENTS.md is an instructions file published in the GitHub repository imjszhang/js-eyes (43 stars, last pushed yesterday), licensed MIT. It adds 1,954 tokens to every session, about $0.0098 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
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).
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.
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).