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 skills/griddynamics/rosetta/documentationnpx skills add griddynamics/rosetta --skill documentationgit clone --depth 1 https://github.com/griddynamics/rosettaWhat 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.00019 | $0.02198 |
| Opus 5 | $0.00010 | $0.01099 |
| Sonnet 5 | $0.00004 | $0.00440 |
| Haiku 4.5 | $0.00002 | $0.00220 |
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 yesterday.
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 — 287 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
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.
4. Minimize duplication aggressively
If content appears in multiple places:
- choose one canonical home
- keep summaries elsewhere very short
- link instead of repeating
5. Optimize for scanning, not reading
Prefer:
- short sections
- direct headings
- decision-oriented wording
- checklists only when they reduce mistakes
- examples only when they remove ambiguity
- structure and order logically
- easy to read
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.
- yesterday First seen · 287 lines · 19 tokens per session scan A f0ab206d65b0
documentation is a skill published in the GitHub repository griddynamics/rosetta (341 stars, last pushed 3d ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,198 once invoked, about $0.0001 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 skills, from other repositories
unity-mcp-orchestrator
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for…
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
signing-entitlements
Inspect signing, entitlements, hardened runtime, and Gatekeeper issues for macOS apps. Use when asked to diagnose code signing failures, missing entitlements, sandbox problems, notarization prerequisites, or trust-policy launch errors.
macos-swiftpm
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
macos-test-triage
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.