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 skills add griddynamics/rosetta --skill init-workspace-verificationgit 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/init-workspace-verification)<a href="https://agentmods.dev/skills/griddynamics/rosetta/init-workspace-verification"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/init-workspace-verification/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.
<a href="https://agentmods.dev/skills/griddynamics/rosetta/init-workspace-verification"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/init-workspace-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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.
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.00010 | $0.00744 |
| Opus 5.5 | $0.00004 | $0.00298 |
| Sonnet 5.5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
init-workspace-verification 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 2mo 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_verification>
Senior workspace initialization auditor
<when_to_use_skill> Final phase of workspace initialization. Consolidates all init-phase outputs into a single completeness audit, runs catch-up for gaps, and revalidates assumptions. </when_to_use_skill>
<core_concepts>
- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
</core_concepts>
Run every checkpoint. Each must pass or have documented justification.
FILE EXISTENCE (non-empty, correct scope):
- TECHSTACK.md — detected technologies, frameworks, build tools
- CODEMAP.md — markdown headers, 3-4 levels, recursive children counts
- DEPENDENCIES.md — direct dependencies only (project, package, version)
- CONTEXT.md — business context only, no technical details
- ARCHITECTURE.md — technical architecture, references CODEMAP.md, no business context
- IMPLEMENTATION.md — current state, DRY references
- ASSUMPTIONS.md — unknowns with forward references
- AGENT MEMORY.md — self-defined purpose and initial entries
- Each document includes self-definition (purpose, content type, style)
INIT INTEGRITY:
- Init mode: exactly one of install, upgrade, plugin
- Composite workspace: top-level docs as registries if composite
- File inventory built before creation/update decisions
- Shell files: frontmatter + single ACQUIRE, zero inline logic
- load-context shell and bootstrap rule installed
- Shells match schema — no structural deviations, no absolute paths
- docs/PATTERNS/ with INDEX.md; each pattern in 2+ locations; INDEX.md is consistent
CROSS-FILE CONSISTENCY:
- TECHSTACK frameworks appear in ARCHITECTURE
- CONTEXT, ARCHITECTURE, IMPLEMENTATION complement — no duplication
- coding.md ACQUIRED FROM KB and used as file creation reference
- greppable headers used in all files
CONDITIONAL (if rules requested, N/A otherwise):
- KB SEARCHED for IDE/Agent rules — agent's built-in knowledge is obsolete, verify KB was queried
- Existing rules checked before creating new
- Root agents file uses bootstrap.md template
- Tech-specific agent files created
- Local instructions with MoSCoW emphasis
- Weekly check mechanism with release version
- Subagents/commands initialized via KB instructions if supported
QUESTIONS:
- HIGH priority gaps addressed via targeted questions
CATCH-UP: For failed checkpoints — identify owning skill, execute, re-verify.
ASSUMPTIONS REVALIDATION:
- Resolved entries: mark with evidence
- Duplicates: keep most detailed
- Forward references: verify target files exist
- New assumptions: track any discovered during verification
DEPRECATED ARTIFACTS (notify user, do NOT auto-delete):
agents/init-rosetta-shells-flow-state.md— r1 state file- Local
init-rosetta-shells-flow.md— replaced by init-workspace-shells skill
</init_workspace_verification>
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.
- 2mo ago First seen · 92 lines · 10 tokens per session scan A aab895343737
init-workspace-verification is a skill published in the GitHub repository griddynamics/rosetta (363 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 744 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.
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.
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.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.