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.
git 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/arrange-workspace-flow-technical-context)<a href="https://agentmods.dev/commands/griddynamics/rosetta/arrange-workspace-flow-technical-context"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/arrange-workspace-flow-technical-context/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/commands/griddynamics/rosetta/arrange-workspace-flow-technical-context"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/arrange-workspace-flow-technical-context.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00019 | $0.00511 |
| Opus 5.5 | $0.00008 | $0.00204 |
| Sonnet 5.5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
arrange-workspace-flow-technical-context 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.
What it actually says
<arrange_workspace_technical_context>
<description_and_purpose>
Interview user to gather technical and architectural facts about the project not yet in docs/ARCHITECTURE.md.
</description_and_purpose>
<phase_steps>
- Interview user about what's missing in
docs/ARCHITECTURE.md— usestarter_topics. Follow Questioning process inhitlSKILL. - Record confirmed answers to
docs/ARCHITECTURE.mdperarchitecture_contract. Unconfirmed inferences →docs/ASSUMPTIONS.md. - Update
arrange-state.md. </phase_steps>
<starter_topics> Starter topics (add project-specific questions as needed):
- How to start the application(s) locally.
- Where and when integration tests and e2e tests are created.
- Any AI agentic harnesses to use.
- Dependencies on external or private libraries.
- Technical and architectural targets.
- Known issues or technical gaps.
- Service dependencies.
- Authentication, authorization, and routing for the deployed application.
- A brief description of the deployment infrastructure and environments.
- The build and CI/CD pipeline.
- Name standards for coding, linting, formatting (e.g. Google Java Style, Microsoft .NET code style) — not the rules!
- Architecture defines how to build/lint/test/run overall solution in concise unambiguous manner. </starter_topics>
<architecture_contract>
- Bulleted technical context, architecture, constraints — engineering perspective
- No business details
- Limit to 100 lines, if there is MORE => keep ARCHITECTURE.md with core ARCHITECTURE plus index to per-feature -ARCHITECTURE.md files with a set of terms what it contains. </architecture_contract>
<validation_checklist>
docs/ARCHITECTURE.mdexists, non-empty, <=100 lines (or indexed).arrange-state.mdupdated. </validation_checklist>
</arrange_workspace_technical_context>
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.
- 1mo ago First seen · 56 lines · 19 tokens per session scan A 3adb7702374b
arrange-workspace-flow-technical-context is a command published in the GitHub repository griddynamics/rosetta (360 stars, last pushed 3d ago), licensed Apache-2.0. It adds 19 tokens to every session and 511 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
deploy-setup
One-time deploy wiring for a fresh storefront. Accepts Shopify's auto-provisioned Oxygen workflow, verifies the validation gate, and confirms readiness.
deploy-check
Pre-flight verification before pushing to main. Reproduces the CI gates locally so the push doesn't fail in production.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.