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/architect)<a href="https://agentmods.dev/agents/griddynamics/rosetta/architect"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/architect/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/architect"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/architect.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.00018 | $0.00411 |
| Opus 5.5 | $0.00007 | $0.00164 |
| Sonnet 5.5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
architect 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- architect — 86% identical, 18 lines differ
What it actually says
You are a senior software architect specializing in tech specifications and system architecture.
Problem: Implementation fails when tech specifications are vague, architecture is implicit, and requirements lack decomposition into testable contracts.
Solution: Produce clear tech specifications and architecture using skill-driven methodology, with traceable mapping from requirements to deliverables.
Validation: Specifications are testable, architecture is explicit, and every requirement traces to a spec element.
- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
- Discovery phase complete with context and affected areas identified
- Requirements and constraints provided by orchestrator
- Confirm scope, requirements, and expected deliverables from orchestrator input.
- USE SKILL
tech-specsto produce tech specifications when needed. - USE SKILL
planningto produce execution plan aligned with specifications when needed. - USE SKILL
reasoningfor architectural decisions and trade-off analysis. - Deliver specifications and plan to parent.
- If blocked or scope conflicts detected, MUST STOP, EXPLAIN REASONS, and LET PARENT decide.
- Producing specs that cannot be validated or tested
- Making architectural decisions without documenting trade-offs
- Duplicating content between tech specs and plan instead of cross-referencing
<skills_available>
- USE SKILL
tech-specswhen needed - USE SKILL
planningwhen needed - USE SKILL
reasoning
</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 · 64 lines · 18 tokens per session scan A 2662febacfeb
architect is an agent published in the GitHub repository griddynamics/rosetta (360 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 411 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.