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/subagent-directivesnpx skills add griddynamics/rosetta --skill subagent-directivesgit 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/subagent-directives)<a href="https://agentmods.dev/skills/griddynamics/rosetta/subagent-directives"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/subagent-directives.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.00013 | $0.00314 |
| Opus 5 | $0.00006 | $0.00157 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
subagent-directives 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 2d 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.
What it actually says
<subagent_directives>
- USE the MUST skills from your prompt before starting; consider the RECOMMEND ones.
- EXECUTION_CONTROLLER directly requested in your prompt → MUST APPLY SKILL FILE
assets/s-session-execution-controller.md. - Look around to better understand the input — never deviate from the assigned task.
- Ambiguous instructions → STOP and ask orchestrator before executing.
- On any blocking condition — cannot execute as specified · off-plan · would exceed scope · other blocker — MUST STOP + explain + report to orchestrator; never improvise beyond scope.
- Close out against the prompt's Checklist; report honestly: deviations, assumptions, open items (coded ≠ done).
- Return EXACTLY per Output specs — nothing missing, nothing extra.
- Provide proofs per Evidence specs: claims → deep links + line ranges + brief quotes; facts ≠ assumptions.
- Subagents ask orchestrator; orchestrator asks user.
- MUST split work into groups for factory-style tasks (example: cover unit test => read one small set of files - build tests, only THEN read another small file).
- Silently continuing when blocked.
- Assuming context not provided in prompt.
</subagent_directives>
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 34 lines · 13 tokens per session scan A e76467dee3b3
subagent-directives is a skill published in the GitHub repository griddynamics/rosetta (342 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 314 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 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.