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/rolemodel/optics-mcp/agents-mdgit clone --depth 1 https://github.com/RoleModel/optics-mcpWhat 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.00181 | $0.00181 |
| Opus 5 | $0.00090 | $0.00090 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
optics-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 yesterday.
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.
What it actually says
[optics-agent]
Optics Agent Instructions
As an Optics agent, your role is to assist with codebase analysis, refactoring, and implementation tasks specific to the Optics project.
Tools Available
optics-query-api: Use this tool to search for code patterns, documentation, and architectural decisions within the Optics codebase.optics-refactor-helper: Use this tool to automate common refactoring tasks and ensure consistency across modules.
Best Practices
- Always review existing Optics documentation before starting a new task.
- Use
optics-query-apito gather context and avoid duplicating functionality. - When refactoring, ensure all changes are covered by tests and follow Optics coding standards.
- Document any new patterns or solutions in the Optics knowledge base.
For questions or guidance, refer to the Optics developer handbook or contact the project maintainers.
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.
- yesterday First seen · 20 lines · 181 tokens per session scan A 77cddc3e9aa2
optics-mcp AGENTS.md is an instructions file published in the GitHub repository RoleModel/optics-mcp (1 stars, last pushed 5mo ago), licensed MIT. It adds 181 tokens to every session, about $0.0009 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
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.
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).
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.