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 commands/griddynamics/rosetta/init-workspace-flow-discoverygit 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/commands/griddynamics/rosetta/init-workspace-flow-discovery)<a href="https://agentmods.dev/commands/griddynamics/rosetta/init-workspace-flow-discovery"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/init-workspace-flow-discovery.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.00016 | $0.01109 |
| Opus 5 | $0.00008 | $0.00554 |
| Sonnet 5 | $0.00003 | $0.00222 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
init-workspace-flow-discovery 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<init_workspace_flow_discovery>
<description_and_purpose> Produces foundational technical documentation (TECHSTACK, CODEMAP, DEPENDENCIES) that all subsequent phases depend on. </description_and_purpose>
<workflow_context>
- Phase 3 of 9 in init-workspace-flow
- Input: filesystem, state.mode, state.composite
- Output: TECHSTACK, CODEMAP, DEPENDENCIES on disk, source code file count
- Count only source code files
- Prerequisite: Phase 1 complete (mode known), Phase 2 complete or skipped </workflow_context>
<phase_steps>
- Read state and confirm mode
- Acquire and execute discovery
- Update state </phase_steps>
<check_mode step="3.1">
- Read
agents/init-workspace-flow-state.md - Confirm Phase 1 complete and mode is set
- If upgrade mode: note which discovery files already exist </check_mode>
<execute_discovery step="3.2">
Act as a senior workspace cartographer — fast, factual technical inventory. Without factual inventory of tech stack, structure, and dependencies, subsequent phases operate blind.
<discovery_process>
- All Rosetta prep steps MUST be FULLY completed, load-project-context skill loaded and fully executed
- Read existing TECHSTACK, CODEMAP, DEPENDENCIES — update if present, create if missing
- Detect languages, frameworks, build tools, package managers, runtime environments → write TECHSTACK
- Existing documentation may be stale or incomplete, prioritize source code artifacts over pre-existing documents
- Generate CODEMAP via shell commands (no pseudo graphics), 3-4 levels deep
- Perform basic discovery yourself with few commands
- Enumerate git repositories yourself
- Markdown headers = workspace-relative path + recursive children count + <10 words description
- List only immediate children files and only with file names
- List target repository source code, static assets, and documentation files based on tech stack
- Exclude noise/caches/build/binary files, files excluded by .gitignore
- Implement as a single shell script in
agents/TEMP/folder - Use
git ls-files --cached --others --exclude-standardin each repository or fallback to find/ls/etc with filters - AVOID manually listing folder-by-folder, either hardcoded script it, or just list entire workspace with both filters to exclude noise folders and include only source code files, then you build map from context
- List direct dependencies (project, package, version) → write DEPENDENCIES
- Preserve human-added sections in existing files
- Update (or create only if missing)
.gitignorein git root folder by adding lines according tobootstrap_rosetta_files(roster in SKILLload-project-context) Minimal set must be present:... # Rosetta agents/TEMP/ refsrc/ !refsrc/INDEX.md - Update (or create only if missing)
.prettierignorein git root folder by adding following lines:... # Rosetta docs/*.md docs/**/*.md
</discovery_process>
DEPENDENCIES.md
- MUST create, use, and maintain flat list of direct project dependencies (project, package, version)
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.
- today First seen · 129 lines · 16 tokens per session scan A a95e8c88a2ef
init-workspace-flow-discovery is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 1,109 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 commands, from other repositories
resolve-conflicts
Resolve merge conflicts on a GitHub PR by merging the base branch into the PR branch in an isolated git worktree, with JSON/markdown-aware conflict resolution.
react-router-client-loader
Do this in a clientLoader and use loaderData to render the component. DO NOT create mock data, new interfaces, or mock data loader functions. Instead, assume loaderData has all of the data you need to render the component.
rclone_archive_extract
Extract archives from source to destination.
rclone_completion
Output completion script for a given shell.
rclone_config_encryption_check
Check that the config file is encrypted.
rclone_config_file
Show path of configuration file in use.