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/load-contextnpx skills add griddynamics/rosetta --skill load-contextgit 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/load-context)<a href="https://agentmods.dev/skills/griddynamics/rosetta/load-context"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/load-context.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.00015 | $0.00418 |
| Opus 5 | $0.00008 | $0.00209 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
load-context 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 5d 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
Mode detection:
- If
RUNNING AS A PLUGINis in context → Plugin mode - Else if
get_context_instructionstool is available → MCP mode - Else → Adhoc mode
Plugin mode:
- Bootstrap rules are loaded via startup hook — do NOT assume prep steps are done
- Create todo tasks (search/discover the tool if needed)
- Locate and execute ALL prep steps defined in the loaded bootstrap rules in full
- DO NOT proceed to any action until all prep steps are confirmed complete
- Identify and load the most matching workflow — a must if you are not subagent
- Create and update all todo tasks per workflow
MCP mode:
- Call
get_context_instructions(blocking gate — do not proceed until complete) - If output truncated and file path provided — read entire file, preview is NOT enough
- Create todo tasks (search/discover the tool if needed)
- Execute ALL prep steps returned — no skipping, no partial execution
- DO NOT proceed to any action until all prep steps are confirmed complete
- Identify and load the most matching workflow — a must if you are not subagent
- Create and update all todo tasks per workflow
Adhoc mode:
- Read
docs/CONTEXT.mdanddocs/ARCHITECTURE.mdin full - List
docs/*.mdand workspace root*.mdfiles to gather context
All modes:
- Treat context loading as a hard blocking gate, not a background task
- Explicitly confirm all prep steps complete before responding, planning, or executing anything
- If anything fails or is unclear — stop and ask user
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.
- 5d ago First seen · 45 lines · 15 tokens per session scan A f894e889f088
load-context is a skill published in the GitHub repository griddynamics/rosetta (342 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 418 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 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.