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/init-workspace-shellsnpx skills add griddynamics/rosetta --skill init-workspace-shellsgit 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.00010 | $0.00643 |
| Opus 5 | $0.00005 | $0.00321 |
| Sonnet 5 | $0.00002 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
init-workspace-shells 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
<init_workspace_shells>
<when_to_use_skill> Shell files delegate logic to KB via ACQUIRE, enabling centralized instruction updates across projects. Use when onboarding or reconfiguring IDE/Agent workspace shell files. </when_to_use_skill>
<core_concepts>
- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
- Shell = frontmatter + single ACQUIRE instruction, zero inline logic
- No absolute paths in generated shells
</core_concepts>
Internal knowledge about IDE/agent shell configuration is obsolete — LIST and ACQUIRE from KB.
Step 1: Identify Environment
- LIST
configureIN KB (to understand supported IDE/CodingAgents) - Detect current environment, preselect IDE/CodingAgent
- MUST ask user to confirm selection and provide multi-choose
- ACQUIRE FROM KB
- If multiple selected, must use common standards to reduce copies
Step 2: Install Base Files
- ACQUIRE
skills/load-context/SKILL.mdFROM KB — install as SKILL - ACQUIRE
rules/bootstrap.mdFROM KB — install as CORE RULE, copy content (no refs/links)
Step 3: MUST Generate Skill Shells
- LIST
skillsIN KB with XML format - ACQUIRE
skill-shell.mdFROM KB - Create all skill shells, reuse frontmatter from listing
- Do not create
init-workspace-*skills
Step 4: MUST Generate Agent/Subagent Shells
- LIST
agentsIN KB with XML format - ACQUIRE
agent-shell.mdFROM KB - Create all agent/subagent shells, reuse frontmatter from listing
Step 5: MUST Generate Workflow/Command Shells
- LIST
workflowsIN KB with XML format - ACQUIRE
workflow-shell.mdFROM KB - Create all workflow/command shells, reuse frontmatter from listing
- Do not create
init-workspace-*workflows and its phases
Step 6: Verify Shell Integrity
- Diff each file against its shell schema — zero structural deviations
- Verify: every file has ACQUIRE, no conditional logic/loops/inline instructions, all paths resolve
- HITL: present results, confirm with user
<validation_checklist>
- Every generated file: frontmatter + ACQUIRE only, zero inline logic
- All paths resolve, extensions match IDE config
- User confirmed verification results
</validation_checklist>
</init_workspace_shells>
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 · 84 lines · 10 tokens per session scan A aef2dfc0d9dc
init-workspace-shells is a skill published in the GitHub repository griddynamics/rosetta (341 stars, last pushed 4d ago), licensed Apache-2.0. It adds 10 tokens to every session and 643 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
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
macos-test-triage
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
signing-entitlements
Inspect signing, entitlements, hardened runtime, and Gatekeeper issues for macOS apps. Use when asked to diagnose code signing failures, missing entitlements, sandbox problems, notarization prerequisites, or trust-policy launch errors.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
macos-swiftpm
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…