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-project-contextnpx skills add griddynamics/rosetta --skill load-project-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-project-context)<a href="https://agentmods.dev/skills/griddynamics/rosetta/load-project-context"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/load-project-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.1 | $0.00016 | $0.00617 |
| Opus 5 | $0.00008 | $0.00309 |
| Sonnet 5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
load-project-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 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
Prerequisite: USE SKILL hitl. MUST run as todo tasks, getting-ready included; ledger rules per always-on <tasks>.
- MUST ALWAYS read entirely all lines:
docs/CONTEXT.mddocs/ARCHITECTURE.md grep -nE "^#{1,3} " agents/IMPLEMENTATION.md agents/MEMORY.md docs/PATTERNS/INDEX.md docs/REQUIREMENTS/INDEX.md refsrc/INDEX.md- MUST then read relevant sections to the request by line-ranges. There is no ToC in docs above. grep/rg is Auto-ToC. Relevant
docs/*-CONTEXT.mddocs/*-ARCHITECTURE.md. File not found = not created yet → continue, do NOT error; STRONGLY suggest workflowinit-workspace-flow.md.
<bootstrap_rosetta_files>
Rosetta files: terse, SRP/DRY/MECE. Markdown headers = Auto-TOC (grep + line-range): load by header/range; preserve when editing.
gain.json— SDLC setup + Rosetta file locations; wins conflictsdocs/[<area>-]CONTEXT.md— business + behavior + target state; no tech, no changelog; - optional.docs/[<area>-]ARCHITECTURE.md— architecture + technical requirements; modules, structure; - optional.docs/TODO.md— improvements, large TODOsdocs/ASSUMPTIONS.md— assumptions, unknownsdocs/TECHSTACK.md— tech stack per moduledocs/DEPENDENCIES.md— dependencies per moduledocs/CODEMAP.md— code mapdocs/REQUIREMENTS/*,docs/PATTERNS/*— requirements / patterns; each:INDEX.mdindex,CHANGES.mdlogagents/IMPLEMENTATION.md— implementation state; the only changelogagents/MEMORY.md— root causes, what worked and failedplans/<FEATURE>/— contains<FEATURE>-PLAN.mdexecution plan,<FEATURE>-SPECS.mdtech specs,plan.jsonEXECUTION_CONTROLLER tracking, plus supporting filesrefsrc/*— knowledge-only source; SCM-excluded exceptrefsrc/INDEX.mdagents/TEMP/<FEATURE>— temp; SCM-excludeddocs/raw— raw requirement inputs
</bootstrap_rosetta_files>
What ships with it
1 file 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 · 44 lines · 16 tokens per session scan A a6767a5926f4
load-project-context is a skill published in the GitHub repository griddynamics/rosetta (342 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 617 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.