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/engineer-profile-lightweight-only-overwritegit clone --depth 1 https://github.com/griddynamics/rosettaWhat 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.00021 | $0.00415 |
| Opus 5 | $0.00010 | $0.00208 |
| Sonnet 5 | $0.00004 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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 today.
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-project-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.
- today First seen · 64 lines · 21 tokens per session scan A bff37f24f7f2
engineer is an agent published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 415 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-09-03.
Other agents, from other repositories
builder
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…
test
Give your AI agent n8n superpowers. 537 nodes with full schemas, 7,700+ templates, Git-like sync, and TypeScript workflows.
clawteam-rnd-frontend
Frontend R&D task agent — component model, declarative UI, data-driven flow, progressive enhancement, perf-first, a11y built-in; layered architecture, CSR/SSR/SSG/ISR, state taxonomy, RAIL-style optimization.
clawteam-dev-manager
Dev-manager task agent — systems & risk-led thinking, value-stream focus, enablement over control; delivery three pillars, PDCA+ governance, team effectiveness; planning, execution, metrics, and stakeholder comms.
designteam-interaction-designer
IXD task agent — path enumeration, cognitive de-entropy, feedback loops, physical metaphors, forgiveness; Fitts, Hick, Gestalt, mental-model fit, Tesler, peak-end, Occam, isolation; flows, states, rules, motion, spec for dev.
avos_hisotry_agent_JSON_converter
You are a strict JSON conversion agent.