Borrowing it
Nothing to install: this file belongs to Pablo-gitub/optees. 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/Pablo-gitub/optees/main/AGENTS.mdgit clone --depth 1 https://github.com/Pablo-gitub/opteesWrote 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/pablo-gitub/optees/agents-md)<a href="https://agentmods.dev/instructions/pablo-gitub/optees/agents-md"><img src="https://agentmods.dev/badge/instructions/pablo-gitub/optees/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/pablo-gitub/optees/agents-md"><img src="https://agentmods.dev/badge/instructions/pablo-gitub/optees/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.00975 | $0.00975 |
| Opus 5.5 | $0.00390 | $0.00390 |
| Sonnet 5.5 | $0.00195 | $0.00195 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
optees 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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Agent Instructions
These instructions apply to every automated coding agent working in this repository. Keep this file concise; detailed and frequently changing project information belongs in the canonical documents linked below.
Sources of truth
Read the relevant source before making changes:
- Architecture and dependency boundaries:
docs/architecture/overview.md - Test strategy, markers, and commands:
docs/guides/testing.md - Versioning, packaging, and release procedure:
docs/guides/releasing.md - Current implementation priorities:
docs/roadmaps/project.mdand any feature-specific roadmap referenced from it
Do not copy large sections of these documents into agent instruction files. When implementation changes behavior, contracts, commands, architecture, supported platforms, or roadmap status, update the corresponding documentation in the same work unit. Documentation must describe shipped behavior honestly; planned functionality must remain clearly marked as planned.
Engineering workflow
- Inspect the surrounding code and existing patterns before designing a change.
- Preserve the dependency direction documented in
docs/architecture/overview.md. Presentation and transport code must not become the owner of domain or solver logic. Register public solver capabilities through the existing composition and versioned-contract mechanisms. - Keep changes scoped. Do not revert, rewrite, or include unrelated user work.
- Prefer existing helpers, codecs, adapters, UI components, and i18n mechanisms over parallel implementations.
- Keep user-visible English and Italian resources synchronized. Do not hardcode translatable UI text.
- Add or update focused tests for changed behavior. Run targeted tests while
iterating, then choose broader gates according to blast radius and
docs/guides/testing.md. Do not claim that tests passed when dependencies, GUI support, sockets, datasets, or platform access prevented execution. - Treat solver correctness, public JSON contracts, independent validation, update behavior, and packaging as high-risk surfaces requiring explicit regression coverage.
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.
- 1mo ago Changed · +20 lines · +221 tokens per session df822cc60fbb
- 2mo ago First seen · 76 lines · 754 tokens per session scan A 31681fcbc441
optees AGENTS.md is an instructions file published in the GitHub repository Pablo-gitub/optees (12 stars, last pushed 19d ago), licensed Apache-2.0. It adds 975 tokens to every session, about $0.0039 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-08-31.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.