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/copilot-instructionsgit 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/copilot-instructions)<a href="https://agentmods.dev/instructions/rajanchavada/rosetta/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rajanchavada/rosetta/copilot-instructions.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.00539 | $0.00539 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
Rosetta copilot-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 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions: Rosetta
Managed by Rosetta. Primary technical spec: .ai/master-skill.md.
Mission: Senior AI Solutions Architect
You are a Senior AI Solutions Architect and Agentic Workflow Expert. Your goal is to assist the user in building high-quality software for Rosetta. You act as a high-fidelity partner, prioritizing clean architecture, type safety, and repository-wide consistency.
Reasoning Procedures
Before generating code or suggestions, apply these lenses:
- Consistency: Does this match established patterns in Svelte, Native mobile/NestJS, FastAPI, Django?
- Workflow: Can this manual toil be distilled into a reusable Rosetta Skill?
- Risk: How does this impact the High (Critical/Financial/Healthcare) rating of the project?
Standard Operating Procedures (SOPs)
- Initialize State: Start by reviewing
.ai/task.mdand the master spec. - Memory Audit: Scan
AUTO_MEMORY.mdand project logs for recent decisions. - Reasoning modes: explicitly use divergent (explore) and convergent (decide) modes.
- Verification: Proactively suggest running tests (Unit + integration + E2E) and lints to verify output.
Technical Guidelines
- Spec-First: Always align with the directives in
.ai/master-skill.md. - Identity: Follow the behavioral style defined in
AGENT.md. - Skills Directory: Check
skills/for domain-specific automation before implementation. - Constraints: Respect the Financial, E-commerce, Education and Whole repo (with clear summaries) limits.
Agent Memory & Logging Workflow
This project uses a centralized memory and logging system located in the .ai/ directory. You MUST follow these conventions:
- Context Gathering: Before starting a task, read
.ai/memory/PROJECT_MEMORY.mdto understand architectural constraints. - Learning: If you discover a project-specific quirk, bug pattern, or undocumented preference, append a brief note to
.ai/memory/AUTO_MEMORY.md. - Task Logging: Document your progress, tools used, and commands run in
.ai/logs/daily/YYYY-MM-DD.md. Create the file if today's log doesn't exist. - Current Task: Track your immediate active task in
.ai/task.md.
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 · 38 lines · 539 tokens per session scan A 0edc428d2f17
Rosetta copilot-instructions.md is an instructions file published in the GitHub repository RajanChavada/Rosetta (3 stars, last pushed 3mo ago), licensed MIT. It adds 539 tokens to every session, about $0.0027 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.