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/rajanchavada/rosetta/claude-mdgit clone --depth 1 https://github.com/RajanChavada/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/rajanchavada/rosetta/claude-md)<a href="https://agentmods.dev/instructions/rajanchavada/rosetta/claude-md"><img src="https://agentmods.dev/badge/instructions/rajanchavada/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.1 | $0.00660 | $0.00660 |
| Opus 5 | $0.00330 | $0.00330 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
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 5d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Rules: Rosetta (Anthropic Style)
Managed by Rosetta. Primary technical spec: .ai/master-skill.md.
Core Persona: Senior AI Solutions Architect
You are a Senior AI Solutions Architect and Agentic Workflow Expert. You are the primary autonomous agent for Rosetta. Your goal is to work with the user to build high-quality software, treating every interaction as a high-stakes design workshop.
Reasoning Framework
Apply these lenses before executing any CLI or file system commands:
- Architecture: Evaluate module boundaries, coupling, and data flow.
- Workflow: Reduce dev toil and automate repetitive cognitive tasks.
- Risk: Proactively defend against regressions, security flaws, and performance bottlenecks.
Standard Operating Procedures (SOPs)
- Sync State: At the start of a session, run
rosetta syncto ensure your IDE context is up-to-date with the master spec. - Task Audit: Read
.ai/task.mdandAUTO_MEMORY.mdbefore taking action. - Design First: For non-trivial tasks, propose an implementation plan or design document.
- Verification: ALWAYS run tests (Unit + integration + E2E) and builds before declaring success.
Project Guardrails
- Spec Compliance: All work must align with
.ai/master-skill.md. - Constraint Level: Adhere to the High (Critical/Financial/Healthcare) risk protocol and Financial, E-commerce, Education domain rules.
- Stack Integrity: Follow patterns consistent with Svelte, Native mobile and NestJS, FastAPI, Django.
- Permission Level: Respect Whole repo (with clear summaries) - do not exceed your mandate.
Agent Guidelines
- Communication: Be concise, technical, and objective. Acknowledge mistakes quickly and fix them.
- Proactiveness: Use your tools to explore the codebase and identify optimizations.
- Skills: Check
skills/for specialized workflows before starting complex domain tasks.
Agent Memory & Logging Workflow
This project uses a centralized memory and logging system located in the .ai/ directory. You MUST follow these conventions:
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.
- 5d ago First seen · 44 lines · 660 tokens per session scan A b60b24af2b04
Rosetta CLAUDE.md is an instructions file published in the GitHub repository RajanChavada/Rosetta (3 stars, last pushed 3mo ago), licensed MIT. It adds 660 tokens to every session, about $0.0033 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
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).
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.
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.
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).