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/where-does-this-gogit 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/where-does-this-go)<a href="https://agentmods.dev/instructions/tikoci/rosetta/where-does-this-go"><img src="https://agentmods.dev/badge/instructions/tikoci/rosetta/where-does-this-go.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.00334 | $0.00334 |
| Opus 5 | $0.00167 | $0.00167 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
rosetta where-does-this-go.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 4d 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
Where does this go?
Use one canonical home for each kind of information:
- Committed codebase work → a GitHub issue. Issues start as discussion; add the
agent-readylabel only once acceptance criteria are settled.umbrella= theme tracking issue,blocked= waiting on a named event. PRs close issues viaCloses #N(seeissue-pr-linking.instructions.md).tasks/is a frozen archive — never add newT-*.mdfiles. - Grounded research or decision support →
briefings/B-*.md - Loose thought with no shape yet →
BACKLOG.mdInbox - Waiting on a specific external event →
BACKLOG.mdTriggers - Durable rationale or architecture tradeoff →
DESIGN.md - Operator, install, release, or re-extraction procedure →
MANUAL.md - Project orientation and routing map →
CLAUDE.md - User-visible shipped behavior →
CHANGELOG.md - Load-bearing invariant and proof →
VALIDATION.md - Agent-specific entrypoint shim →
AGENTS.mdor.github/copilot-instructions.md, pointing back toCLAUDE.md
Other files should point at the canonical home, not restate it.
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.
- 4d ago First seen · 21 lines · 334 tokens per session scan A d8f753c5d883
rosetta where-does-this-go.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 18d ago), licensed MIT. It adds 334 tokens to every session, about $0.0017 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
vscode-agent-todos copilot-instructions.md
Instructions for digitarald/vscode-agent-todos, covering project overview, important, architecture, performance optimizations and event system architecture.
bun-mcp copilot-instructions.md
Copilot instructions for TomasHubelbauer/bun-mcp, covering github copilot instructions for the bun-mcp repository and formatting.
vscode-agent-todos CLAUDE.md
Instructions for digitarald/vscode-agent-todos, a project described as: Gives VS Code agent mode planning superpowers with dynamic todo lists.
plugin-files-mode
Rosetta Plugin Mode Bootstrap.
mcp-redmine-rest CLAUDE.md
Claude Code instructions for alsimoes/mcp-redmine-rest, covering claude.md, what this is, layout (src-layout), tool registration pattern and deliberately missing tools.
onplana-mcp-server GEMINI.md
Instructions for Onplana/onplana-mcp-server, covering onplana, gemini context, what onplana is, authenticating, hints when working with onplana data and common workflows.