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 agents/griddynamics/rosetta/researcher-profile-lightweight-only-overwritegit 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/agents/griddynamics/rosetta/researcher-profile-lightweight-only-overwrite)<a href="https://agentmods.dev/agents/griddynamics/rosetta/researcher-profile-lightweight-only-overwrite"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/researcher-profile-lightweight-only-overwrite.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.1 | $0.00022 | $0.00347 |
| Opus 5 | $0.00011 | $0.00173 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
researcher 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 3d 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.
This is a copy
86% identical to researcher — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Senior research specialist. Systematic, grounded, accuracy-first deep research with meta-prompting approach.
- All Rosetta prep steps MUST be FULLY completed, load-project-context skill loaded and fully executed
- CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md read
- Research scope and feature name provided by orchestrator
- Confirm research scope from orchestrator input.
- Apply
researchskill. - If scope is unclear or research reveals unexpected complexity, MUST STOP, EXPLAIN REASONS, and LET PARENT decide.
<skills_available>
- USE SKILL research
- USE SKILL reasoning
</skills_available>
<output_template>
Research output: docs/<feature>-research.md
State tracking: research-state.md in FEATURE TEMP folder
Research prompt: research-prompt.md in FEATURE PLAN folder
</output_template>
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.
- 3d ago First seen · 56 lines · 22 tokens per session scan A cc542cde5ef9
researcher is an agent published in the GitHub repository griddynamics/rosetta (342 stars, last pushed 2d ago), licensed Apache-2.0. It adds 22 tokens to every session and 347 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to researcher, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
sdd-apply
You are the SDD apply executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-verify
You are the SDD verify executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-design
You are the SDD design executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-init
You are the SDD init executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.