agentmods.dev

init-workspace-shells

init-workspace-shells is a skill for Claude Code from griddynamics/rosetta. It costs 10 tokens per session (643 once invoked), scanned A, original, Apache-2.0.

A setup helper that creates shell files for coding-agent or IDE workspaces. These files point to shared instructions instead of copying the instructions into every project.

In plain words
What is it for?
Use it when onboarding a workspace or changing its coding-agent or IDE configuration. It can install base instruction files and generate shells for available skills.
Why use it?
It keeps workspace setup consistent and lets shared instructions be updated centrally. It also avoids hard-coded computer-specific paths in generated files.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: model in frontmatter; mentions subagents.

not rated 360repo +6 yesterday A scan SkillSpector: warn 10 tokens original Apache-2.0

Good fit Use it when onboarding a workspace or changing its coding-agent or IDE configuration. It can install base instruction files and generate shells for available skills.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/griddynamics/rosetta/init-workspace-shells
View source ↗ griddynamics/rosetta griddynamics.github.io
Install

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.

Any agent
npx skills add griddynamics/rosetta --skill init-workspace-shells
Clone the repo
git clone --depth 1 https://github.com/griddynamics/rosetta

Made for: Claude Code.

Wrote 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.

agentmods badge for init-workspace-shells

README.md
[![agentmods](https://agentmods.dev/badge/skills/griddynamics/rosetta/init-workspace-shells/github.svg)](https://agentmods.dev/skills/griddynamics/rosetta/init-workspace-shells)
Your own site
<a href="https://agentmods.dev/skills/griddynamics/rosetta/init-workspace-shells"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/init-workspace-shells/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for init-workspace-shells

Your own site · 80×15
<a href="https://agentmods.dev/skills/griddynamics/rosetta/init-workspace-shells"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/init-workspace-shells.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 643 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 7
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
  • medium Agent Snooping · line 44
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00643
Opus 5.5 $0.00004 $0.00257
Sonnet 5.5 $0.00002 $0.00129
Haiku 4.5 $0.00001 $0.00064

Measured 1mo ago against content hash aef2dfc0d9dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

instructions/r2/core/skills/init-workspace-shells/SKILL.md · 84 lines

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

  1. LIST configure IN KB (to understand supported IDE/CodingAgents)
  2. Detect current environment, preselect IDE/CodingAgent
  3. MUST ask user to confirm selection and provide multi-choose
  4. ACQUIRE FROM KB
  5. If multiple selected, must use common standards to reduce copies

Step 2: Install Base Files

  1. ACQUIRE skills/load-context/SKILL.md FROM KB — install as SKILL
  2. ACQUIRE rules/bootstrap.md FROM KB — install as CORE RULE, copy content (no refs/links)

Step 3: MUST Generate Skill Shells

  1. LIST skills IN KB with XML format
  2. ACQUIRE skill-shell.md FROM KB
  3. Create all skill shells, reuse frontmatter from listing
  4. Do not create init-workspace-* skills

Step 4: MUST Generate Agent/Subagent Shells

  1. LIST agents IN KB with XML format
  2. ACQUIRE agent-shell.md FROM KB
  3. Create all agent/subagent shells, reuse frontmatter from listing

Step 5: MUST Generate Workflow/Command Shells

  1. LIST workflows IN KB with XML format
  2. ACQUIRE workflow-shell.md FROM KB
  3. Create all workflow/command shells, reuse frontmatter from listing
  4. Do not create init-workspace-* workflows and its phases

Step 6: Verify Shell Integrity

  1. Diff each file against its shell schema — zero structural deviations
  2. Verify: every file has ACQUIRE, no conditional logic/loops/inline instructions, all paths resolve
  3. 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>

Changes

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.

  1. 1mo ago First seen · 84 lines · 10 tokens per session scan A aef2dfc0d9dc

Subscribe to this mod's changes

init-workspace-shells is a skill published in the GitHub repository griddynamics/rosetta (360 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 643 once invoked, about $0.0000 per session on Opus 5.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.

Claude Codecodexconfigurecopilotcursordeveloper-toolsinitmcp-servershellsworkspace
Related

Other skills, from other repositories

memorix-memory

Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.

AVIDS2/memorix · 30 tokens

memorix

Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.

AVIDS2/memorix · 34 tokens

memorix-mini-skills

Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.

AVIDS2/memorix · 30 tokens

memorix-orchestrate

Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.

AVIDS2/memorix · 37 tokens

memorix-troubleshooting

Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.

AVIDS2/memorix · 36 tokens

memorix-git-memory

Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.

AVIDS2/memorix · 31 tokens