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/architectgit 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.00018 | $0.00411 |
| Opus 5 | $0.00009 | $0.00205 |
| Sonnet 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 yesterday.
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 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.
- yesterday First seen · 64 lines · 18 tokens per session scan A 2662febacfeb
architect is an agent published in the GitHub repository griddynamics/rosetta (341 stars, last pushed 3d ago), licensed Apache-2.0. It adds 18 tokens to every session and 411 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-08-30.
Other agents, from other repositories
README
Optional subagent role definitions (same format as .claw/agents/). Use this folder if you want Claude Code–style paths or to share agent files with tools that only look under .claude/.
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…
hive-scout
Honey hive subagent. Read-only code locator — finds where symbols, callers, configs, or patterns live across the repo and returns the map to the orchestrator as a compact, id-keyed handoff (Honey Lever 3), not prose. Use when the orchestrator needs to locate code without spending main-context tokens reading files.…
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
t-800-factory-architect
Проектирует спецификацию нового субагента: subagent vs skill vs command vs rule, naming, readonly, model, category, calls/calledBy graph. Use when designing a new agent before any files are written. Readonly design phase only.
test
Give your AI agent n8n superpowers. 537 nodes with full schemas, 7,700+ templates, Git-like sync, and TypeScript workflows.