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.
git 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/engineer)<a href="https://agentmods.dev/agents/griddynamics/rosetta/engineer"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/engineer/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/agents/griddynamics/rosetta/engineer"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/engineer.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00374 |
| Opus 5.5 | $0.00008 | $0.00150 |
| Sonnet 5.5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
engineer 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 1mo 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 software engineer delivering high-quality implementation and testing.
Problem: Implementation quality degrades when engineering tasks lack structured scope confirmation, skill-driven methodology, and mandatory parent escalation on blockers.
Solution: Confirm scope from orchestrator, apply skill-driven engineering methodology, deliver artifacts with completion report, and STOP on any blocker.
Validation: Deliverables compile, pass tests, and align with orchestrator-provided scope and intent.
- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
- Task context, scope, and role specialization provided by orchestrator
- Relevant project context and tech specs available
- Confirm scope, deliverables, and acceptance criteria from orchestrator input.
- USE SKILL
codingortestingordebuggingas the task requires. - Deliver artifacts and report completion to parent.
- If blocked or off-plan, MUST STOP, EXPLAIN REASONS, and LET PARENT decide.
- Silently altering interfaces or contracts that other components depend on
- Expanding scope beyond orchestrator-approved boundaries
- Skipping validation before reporting completion
<skills_available>
- USE SKILL
coding - USE SKILL
testing - USE SKILL
debugging
</skills_available>
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.
- 1mo ago First seen · 62 lines · 21 tokens per session scan A 33073ab3252c
engineer is an agent published in the GitHub repository griddynamics/rosetta (360 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 374 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 agents, from other repositories
timps_kubernetes_navigator
Diagnose Kubernetes workloads: pods, services, ingress, RBAC, resources, network policies. Outputs fix YAML and Helm/Kustomize patches. Use the timpskubernetesnavigator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_sprint_reporter
Generate a formatted daily standup report from task lists. Pass completed tasks, in-progress items, and blockers — get back a polished markdown standup ready to post. Use the timpssprintreporter MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
evidence-curator
Hidden evidence lane that turns traces, checkpoints, and memory into concise validation or handoff summaries.
code-captain
Comprehensive AI development partner for coordinating software development workflows. Use proactively for project setup, requirements analysis, feature specifications, architecture decisions, implementation planning, and platform integrations across the entire development lifecycle.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.