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/tikoci/rosetta/instruction-scopesgit clone --depth 1 https://github.com/tikoci/rosettaWhat 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.00184 | $0.00184 |
| Opus 5 | $0.00092 | $0.00092 |
| Sonnet 5 | $0.00037 | $0.00037 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
rosetta instruction-scopes.instructions.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 2d 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.
What it actually says
Instruction scopes
When adding or editing instruction or agent-entrypoint files:
- Put one rule or one tightly related topic in each file.
- Use the smallest honest
applyToscope; broad scopes are fine when the rule is genuinely broad. - Keep one normative home per rule. Other instruction files should point to it instead of copying the prose.
- Prefer adding a new narrow file over inflating a generic router file.
- Keep
CLAUDE.md,AGENTS.md, and.github/copilot-instructions.mdas thin routers, not competing rulebooks.
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.
- 2d ago First seen · 14 lines · 184 tokens per session scan A 86a5bba42be3
rosetta instruction-scopes.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 16d ago), licensed MIT. It adds 184 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-30.
Other instructions, from other repositories
bun-mcp copilot-instructions.md
Copilot instructions for TomasHubelbauer/bun-mcp, covering github copilot instructions for the bun-mcp repository and formatting.
memorix GEMINI.md
Instructions for AVIDS2/memorix, covering memorix - cross-agent memory rules, session start - bind project, then load context, during session - capture important context, architecture & decisions and bug fixes & problem solving.
calc-mcp CLAUDE.md
Instructions for coo-quack/calc-mcp, covering project rules, tech stack, commands, project structure and tool architecture.
mcp-security-scanner CLAUDE.md
Instructions for badchars/mcp-security-scanner, covering mcp-security-scanner — mcp security scanner, architecture, key rules, tool categories (43 tools) and commands.
relay AGENTS.md
Instructions for ImBIOS/relay, covering agents.md — relay, project overview, tech stack, architecture and support policy.
copilot-mcp CLAUDE.md
Claude Code instructions for VikashLoomba/copilot-mcp, covering claude.md, project overview, development commands, root directory commands and install dependencies for both extension and web ui.