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/tasks-vs-briefingsgit 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/tasks-vs-briefings)<a href="https://agentmods.dev/instructions/tikoci/rosetta/tasks-vs-briefings"><img src="https://agentmods.dev/badge/instructions/tikoci/rosetta/tasks-vs-briefings.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.00265 | $0.00265 |
| Opus 5 | $0.00133 | $0.00133 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
rosetta tasks-vs-briefings.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 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.
What it actually says
Issues vs briefings (tasks/ is archived)
The canonical detailed rules live in tasks/README.md (archive note + issue-queue summary) and briefings/README.md.
- GitHub Issues are the work commitments — discussion first,
agent-readylabel once the spec is settled. Acceptance criteria still citeV-*rows fromVALIDATION.md. briefings/B-*.mdare research or decision-support notes that may conclude with "do nothing" or "opened issue #N."BACKLOG.mdis the loose-thought / trigger layer, not a substitute tracker.tasks/T-*.mdis a frozen archive (migration: issue #18). Never create new task files;tasks/done/files stay for grep-able history. Sole in-flight exception:T-0037.
If you need the fine print, read the directory README that owns the file you are editing.
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 · 15 lines · 265 tokens per session scan A a32e526361ef
rosetta tasks-vs-briefings.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 19d ago), licensed MIT. It adds 265 tokens to every session, about $0.0013 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.
rosetta AGENTS.md
AGENTS.md instructions for griddynamics/rosetta: Main goal: cover E2E AI PDLC engineering workflows at foundation level for AI-First SDLC in enterprise. Top-level or orchestrator agents MUST READ docs/ARCHITECTURE.md contains technical details and guidance, and docs/CONTEXT.md - business context. Subagents - when…
mcp-server-azure-devops AGENTS.md
Instructions for Tiberriver256/mcp-server-azure-devops: /home/tiberriver256/repos/mcp-server-azure-devops/docs/important-knowledge/azure-devops-rest-api-research.md Researching Azure DevOps REST APIs, selecting api-version, or handling Azure DevOps Server (on-prem) endpoints.
plugin-files-mode
Rosetta Plugin Mode Bootstrap.
calc-mcp CLAUDE.md
Claude Code instructions for coo-quack/calc-mcp, covering project rules, tech stack, commands, project structure and tool architecture.
mcp-security-scanner CLAUDE.md
Claude Code instructions for badchars/mcp-security-scanner, covering mcp-security-scanner — mcp security scanner, architecture, key rules, tool categories (43 tools) and commands.