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/claude-mdgit clone --depth 1 https://github.com/tikoci/rosettaWrote 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/tikoci/rosetta/claude-md)<a href="https://agentmods.dev/instructions/tikoci/rosetta/claude-md"><img src="https://agentmods.dev/badge/instructions/tikoci/rosetta/claude-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.01455 | $0.01455 |
| Opus 5 | $0.00727 | $0.00727 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
rosetta CLAUDE.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 3d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rosetta
RouterOS documentation as SQLite FTS5 — one core data model exposed through three surfaces: an MCP server for agents, a browse TUI for humans, and a command-tree/glossary layer for downstream RouterOS tooling. This file is intentionally a thin routing index. Detailed rationale lives in DESIGN.md; install and operator reference live in MANUAL.md; narrow coding rules live in .github/instructions/*.instructions.md.
Project Documentation
Each file has one job. Prefer the canonical home instead of inventing a new top-level .md.
| File / dir | Canonical role |
|---|---|
CLAUDE.md |
Project orientation + routing index for agents |
AGENTS.md |
Short Codex-specific routing note |
DESIGN.md |
Durable rationale, data-source provenance, architecture tradeoffs |
MANUAL.md |
Install, operations, release/re-extraction steps, schema reference |
README.md |
User-facing quick start |
CHANGELOG.md |
User-visible shipped changes under [Unreleased] / releases |
VALIDATION.md |
Load-bearing invariants and how CI proves them |
BACKLOG.md |
Lightweight inbox, triggers, and briefing index |
| GitHub Issues | Active committed work items (agent-ready / umbrella / blocked labels) |
tasks/ |
Frozen archive of the pre-2026-07 file-based queue; tasks/done/T-*.md kept for grep-able history. No new task files |
briefings/B-*.md |
Research notes and decision support |
.github/copilot-instructions.md |
Short Copilot-specific routing note |
.github/instructions/*.instructions.md |
Narrow normative rules matched by applyTo |
.github/prompts/*.prompt.md |
Repo-local Copilot prompt workflows |
.github/skills/*/SKILL.md |
Repo-local skill workflows — canonical home; symlinked into .claude/skills/ so Claude Code triggers them too (same real-dir+symlink convention as the global routeros-* skills in ~/CLAUDE.md) |
Where does this go?
The canonical routing rule lives in .github/instructions/where-does-this-go.instructions.md. Short version:
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.
- 3d ago First seen · 68 lines · 1,455 tokens per session scan A 03fafb1d9829
rosetta CLAUDE.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 17d ago), licensed MIT. It adds 1,455 tokens to every session, about $0.0073 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 CLAUDE.md
Instructions for AVIDS2/memorix, covering memorix - agent instructions for claude code, using memorix memory tools, when to search memory, when to store memory and when to resolve memory.
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.