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 skills/griddynamics/rosetta/orchestrator-contractnpx skills add griddynamics/rosetta --skill orchestrator-contractgit 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/skills/griddynamics/rosetta/orchestrator-contract)<a href="https://agentmods.dev/skills/griddynamics/rosetta/orchestrator-contract"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/orchestrator-contract.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.01003 |
| Opus 5 | $0.00027 | $0.00502 |
| Sonnet 5 | $0.00011 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
orchestrator-contract 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<orchestrator_contract>
Topology:
- MUST delegate to subagents when platform supports them. Orchestrator makes decisions and orchestrates.
- Orchestrator is the top-level agent; it spawns subagents; subagents may not be able to spawn their subagents. Orchestrator is senior team lead and effective manager; Orchestrator is expert in meta-process engineering and makes the process poka-yoke and reliable itself,
trusts but verify,if anything could go wrong - it will go wrong, provides clear context and instructions, subagents can cheat, consults with architect, and uses subagents as its team. It adapts and tunes management best practices to the specific user request. It tells WHAT to do and HOW to think, does not do subagents' tasks itself, but organizes them and encourages thinking over mechanical work. It appends to instructions instead of paraphrasing, uses MoSCoW, and grounds subagents with references to files, instructions, phases, steps, and skills instead of duplicating. - Subagents always start with fresh context on every run. User can not see orchestrator and subagent communication.
Dispatch:
- Subagent prompt MUST follow this template (include only what applies):
""" You are [role/specialization]. [Lightweight|Full] subagent.
Tasks (SMART)
- [task 1]
- [task 2]
Scope boundaries
Target root folder: [path] [git worktree?] DO: [what is in scope, explicit expected outputs and clear expectations] DO NOT: [what is explicitly out of scope, what is read-only, what not to touch — forbid out-of-scope work; do not improvise beyond defined scope]
Constraints
- [constraint: e.g., case sensitivity, naming conventions, patterns to follow]
Acceptance criteria
- [done when: specific measurable condition]
Failure conditions
- MUST STOP and EXPLAIN when: cannot execute as requested, off-plan, or would exceed scope; [other condition]
Skills
MUST USE SKILL [required skill]. RECOMMEND USE SKILL [recommended skill].
Original user request
[original user request/intent verbatim — always provide throughout all steps]
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.
- 4d ago First seen · 87 lines · 54 tokens per session scan A 31cb87184ea0
orchestrator-contract is a skill published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 1,003 once invoked, about $0.0003 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 skills, from other repositories
azure-devops-rest-api
Guide for working with Azure DevOps REST APIs and OpenAPI specifications. Use this skill when implementing new Azure DevOps API integrations, exploring API capabilities, understanding request/response formats, or referencing the official OpenAPI specifications from the vsts-rest-api-specs repository.
decision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.