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/sync-web-sitenpx skills add griddynamics/rosetta --skill sync-web-sitegit 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.00016 | $0.02707 |
| Opus 5 | $0.00008 | $0.01354 |
| Sonnet 5 | $0.00003 | $0.00541 |
| Haiku 4.5 | $0.00002 | $0.00271 |
Grade A, and why
sync-web-site scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Local Jekyll preview:** first run needs `bundle install` (gems aren't vendored in the repo). Then `cd docs/web && bundle exec jekyll serve --detach --port <port>`. Fetch pages with `curl -s http://127.0.0.1:<port>/ro How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a web site senior engineer and public OSS documentation expert.
Your job is to synchronize and improve documentation clarity, simplicity, and 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
Avoid:
- essays
- repeated background
- generic Git tutorials
- long motivational text
- policy dumps in operational docs
For each document, define:
- primary audience
- primary question it answers
- allowed content
- excluded content
You provide best practices and reasoning frameworks, not arbitrary opinions.
Operating rules
0. Prerequisites
- Grep md headers and read entire
## Reader profilessection using line ranges of docs/reviews/DOC-STRUCTURE-PLAN.md - Read the rest when needed later on (!)
1. Identify changes to workspace root .md, docs/.md, docs/web/* files
- Use git to query last 5 days of commits with changes in target files
- Understand a reason why it was changed
- Understand what was already updated
2. Find respective files in docs/web/*
- Use grep/search
- Understand context in each case
- Define what and how should be integrated in each document
3. HITL
- Present recommendations and plan with exact was-became mapping
- Explicit approval only, Questions are not approval
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.
- 2d ago First seen · 143 lines · 16 tokens per session scan A ee36b60f9e4c
sync-web-site is a skill published in the GitHub repository griddynamics/rosetta (341 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 2,707 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
macos-swiftui-patterns
Build macOS SwiftUI scenes and components with desktop patterns. Use when shaping windows, commands, toolbars, settings, split views, or inspectors.
build-and-run-macos-app
Slash command that creates or updates the project-local macOS script/buildandrun.sh and uses it as the default build/run entrypoint. Invoke explicitly with /build-and-run-macos-app — this skill never self-triggers.
macos-test-triage
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
macos-packaging-notarization
Prepare macOS packaging and notarization workflows. Use when archiving apps, validating bundles, or explaining distribution-only failures.
macos-swiftpm
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
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.