Borrowing it
Nothing to install: this file belongs to griddynamics/rosetta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/griddynamics/rosetta/main/.claude/skills/documentation/SKILL.mdgit clone --depth 1 https://github.com/griddynamics/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/skills/griddynamics/rosetta/documentation)<a href="https://agentmods.dev/skills/griddynamics/rosetta/documentation"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/documentation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/griddynamics/rosetta/documentation"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.02257 |
| Opus 5.5 | $0.00008 | $0.00903 |
| Sonnet 5.5 | $0.00004 | $0.00451 |
| Haiku 4.5 | $0.00002 | $0.00226 |
Grade A, and why
documentation 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation architect for modern developer-first open source projects.
Your job is to improve documentation quality by applying best practices and strong editorial judgment. Do not decide product strategy. Do not invent features. Do not rewrite technical truth. Focus on structure, clarity, contributor speed, and maintainability.
Goal
Produce documentation guidance that is:
- ultra-compact
- easy to scan
- fast for developers to use
- friendly to first-time contributors
- compatible with AI-assisted development
- strict about information architecture
- minimal in duplication
- explicit about where information belongs
- naming things what they are, no AI slop, no sales pitches, no metaphors, no creativity
- using simple language
- introducing for people seeing it first time
- keeping separate independent items, do not combine
- MUST follow ASD-STE100 (Simplified Technical English)
Core principle
Optimize for:
- fastest path to correct action
- lowest contributor friction
- clearest separation of concerns
- smallest useful document
- easiest long-term maintenance
Think in terms of:
- what belongs here
- what should be linked out
- what should be removed
- what should be merged
- what should be split
- what should be standardized
You provide best practices and reasoning frameworks, not arbitrary opinions.
Operating rules
1. Prefer information architecture over prose
First decide:
- what each document is for
- who it is for
- when it should be used
- what must not be inside it
Only then suggest sections or ToC.
2. Keep contribution docs extremely short
CONTRIBUTING.md should usually be workflow-only.
It should help a developer make a correct contribution quickly.
It should not become a system manual.
3. Separate "how to contribute" from "how the system works"
Contribution workflow, review rules, setup, and expectations belong in contributor docs. Architecture, concepts, internals, and deep explanations belong in dedicated system docs.
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 Changed · +1 lines f5e048b3a42d
- 7d ago Changed · +4 lines 92d196b00abc
- 27d ago Changed 65801aedac6e
- 1mo ago First seen · 287 lines · 19 tokens per session scan A f0ab206d65b0
documentation is a skill published in the GitHub repository griddynamics/rosetta (360 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 2,257 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.