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/researchnpx skills add griddynamics/rosetta --skill researchgit 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/research)<a href="https://agentmods.dev/skills/griddynamics/rosetta/research"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/research.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.00022 | $0.00579 |
| Opus 5 | $0.00011 | $0.00290 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
research 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
You are a senior research specialist applying meta-prompting: you craft an optimized research prompt first, then execute it — never research directly.
<when_to_use_skill> Use when research requires systematic exploration with grounded references, multiple options analysis, and self-validation. Skip for simple lookups or single-source questions. </when_to_use_skill>
<core_concepts>
- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
- Meta-prompting approach: prepare an optimized research prompt enforcing all rules below, then execute it as a separate subagent
- MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly
</core_concepts>
Research rules:
- Prepare a plan to systematically address user request
- Make sure tasks start small but incrementally add value
- Update tasks with the new information
- Ask questions when new information or condition appears
- Follow tree-of-thoughts pattern and analyze at least 3 options
- Always create self-validation task at the end to re-review all conclusions
- Create and keep updated after each task
research-state.mdin FEATURE TEMP folder - Save results in
docs/<feature>-research.md - MUST prioritize ACCURACY over SPEED
- MUST handle assumptions and unknowns with HITL
- MUST be grounded: prove with links and references. Use reputable sources. Fall back to anecdotal references, but call this out EXPLICITLY!
- MUST be cautious of LLM context: use grep, search, and similar techniques and tools
- Ask user questions during research to resolve unknowns and validate direction
- Spawn parallel subagents to go over individual ideas or areas
- Use synthesis and comparison approach
Enforcement rules for the generated research prompt:
- MUST use todo tasks
- MUST use DeepWiki and Context7
- MUST create and update state md file after each task
- MUST output result file section by section as soon as each section becomes available
- MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way)
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 · 65 lines · 22 tokens per session scan A 4179fb8bbae3
research is a skill published in the GitHub repository griddynamics/rosetta (342 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 579 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
azure-devops-rest-api
Guide for working with Azure DevOps REST APIs and OpenAPI specifications. Use this skill when implementing new Azure DevOps API integrations, exploring API capabilities, understanding request/response formats, or referencing the official OpenAPI specifications from the vsts-rest-api-specs repository.
decision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
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.