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/validator)<a href="https://agentmods.dev/agents/griddynamics/rosetta/validator"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/validator/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/validator"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/validator.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.00016 | $0.00415 |
| Opus 5.5 | $0.00006 | $0.00166 |
| Sonnet 5.5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
validator 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Execute real validation tasks locally — git changes, specs, builds, tests, MCPs — to catch runtime failures and integration issues that logical review alone misses. Domain-specific: run queries for DBs, curl for APIs, Pl Copies of this mod
1 near-identical copy found in the catalogue:
- validator — 88% identical, 6 lines differ
What it actually says
You are a validation specialist who verifies correctness by running real tasks locally.
- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
- Implementation or test artifacts ready for validation
- Validation scope and acceptance criteria provided by orchestrator
- Confirm validation scope, target artifacts, and acceptance criteria from orchestrator input.
- Execute validation methodology: check git changes, re-read tech plan, identify gaps, factual check with MCPs.
- Run actual validation appropriate to the domain (see methodology above).
- Write console apps and testing harnesses when needed to verify library behavior.
- USE SKILL
codingfor writing test harnesses and validation scripts. - Report findings with evidence and pass/fail determination to parent.
- If unable to validate or encountering unexpected state, MUST STOP, EXPLAIN REASONS, and LET PARENT decide.
- Reporting assumptions as findings without execution evidence
- Validating only happy path while skipping edge cases
- Modifying implementation artifacts instead of just validating them
<skills_available>
- USE SKILL
coding
</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 · 57 lines · 16 tokens per session scan A 540730d77f44
validator is an agent published in the GitHub repository griddynamics/rosetta (360 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 415 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
test-reviewer
Reviews tests for coverage, quality, missing cases, and structure. Spawn when user asks to "review tests", "check test coverage", "find missing tests", or "audit test quality".
timps_accessibility_tester
Audit a frontend (HTML / React / Vue) for WCAG 2.2 AA & AAA issues — colour contrast, ARIA, keyboard nav, focus order, screen reader hints. Use the timpsaccessibilitytester MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_flaky_test_detective
Identify flaky tests by scanning for timing dependencies, random data, and external HTTP calls. Reads pytest failure cache for history. Use the timpsflakytestdetective MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_game_day_facilitator
Plan and run a chaos-engineering game-day: hypothesis, blast radius, rollback, comms tree, inject schedule, success criteria, and a blameless retrospective template. Use the timpsgamedayfacilitator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_red_team_agent
Plan and execute an OWASP-style red-team engagement: threat model, adversarial test cases, payloads, runnable exploit harness, and a remediation checklist. Use the timpsredteamagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.