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-questionsgit 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.00016 | $0.00425 |
| Opus 5 | $0.00008 | $0.00212 |
| Sonnet 5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
init-workspace-flow-questions 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.
What it actually says
<init_workspace_flow_questions>
<description_and_purpose>
Problem: Automated analysis leaves gaps — ambiguous domain logic, unstated conventions, missing rationale. Validation: Every accumulated gap has a resolution; each answer traces to at least one file update.
</description_and_purpose>
<workflow_context>
- Phase 8 of 9 in init-workspace-flow
- Input: all docs from Phases 1–7, accumulated gaps from state
- Output: answers integrated into docs, affected files updated directly
- These are intentional questions to the USER, auto mode / no approvals / etc ARE NOT APPLICABLE
</workflow_context>
<phase_steps>
- Read state and accumulated gaps
- Review all created docs for gaps and contradictions
- Ask user reflective questions
- Map answers to affected files
- Update affected files
- Ask critical/high/major impact questions
- Prioritize by impact: scope > security/privacy > UX > technical
- Ask few independent questions at a time, if question can be searched, checked in code, do that first
- Adjust and interview user relentlessly about every aspect of the workspace until you reach a full shared understanding
- User is allowed to skip and leave items unresolved, but this must be highly discouraged
- Keep facts, document concise, valuable, highly compressed, cut wording, use terms and common patterns
- Update state — clear resolved gaps, note unresolved
</phase_steps>
- Auto mode classifier defers user questions
- Do not re-ask questions answered as in-phase blockers — check state
- Unanswered questions: log as deferred gap, do not guess
</init_workspace_flow_questions>
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 · 54 lines · 16 tokens per session scan A 0bfde217ac2b
init-workspace-flow-questions 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 425 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
full-review-gate
Perform a comprehensive repository code review in an isolated worktree. Fix P0/P1 findings and ship them as a PR targeting the current branch.
implement-fastapi-routes
The file docstring contains a description of the FastAPI routes we need to implement. Implement these routes.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
init-store
Clone the canonical Hydrogen starter, brand it, pin @commerce-atoms/agents, and create the first commit.
hook-install
Install a git hook for automatic commit sync on push. When installed, every git push automatically syncs pushed commits to Avos Memory, enabling real-time team synchronization.
commit
Use the text the user typed after the command name as the request for this command.