arrange-workspace-flow-reference-source-code

arrange-workspace-flow-reference-source-code is a command for coding agents from griddynamics/rosetta. It costs 20 tokens per session (583 once invoked), scanned A, original, Apache-2.0.

Phase 2 Reference Source Code of arrange-workspace-flow.

Command

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.

agentmods
npx agentmods add commands/griddynamics/rosetta/arrange-workspace-flow-reference-source-code
Clone the repo
git clone --depth 1 https://github.com/griddynamics/rosetta
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 583 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00020 $0.00583
Opus 5 $0.00010 $0.00292
Sonnet 5 $0.00004 $0.00117
Haiku 4.5 $0.00002 $0.00058

Measured today against content hash 542994b2fd31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

arrange-workspace-flow-reference-source-code 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.

plugins/core-copilot-light/commands/arrange-workspace-flow-reference-source-code.md · 62 lines

What it actually says

<arrange_workspace_reference_source_code>

<description_and_purpose> Onboard read-only reference code the agent cannot otherwise see into refsrc/, documented in refsrc/INDEX.md. </description_and_purpose>

<phase_steps>

  1. Identify existing reference source code
  2. Validate it is defined correctly, fix gaps
  3. Ask user for additional reference source code
  4. Validate and finalize what user provides </phase_steps>

<identify_existing step="2.1">

  1. Read docs/ARCHITECTURE.md/docs/CONTEXT.md for mentions of external/reference code, if they already exist.
  2. List existing refsrc/* folders and existing refsrc/INDEX.md entries. </identify_existing>

<validate_existing step="2.2">

  1. Confirm root .gitignore has these exceptions; add any missing:
agents/TEMP/
refsrc/
!refsrc/INDEX.md
  1. Confirm every refsrc/* folder has a matching refsrc/INDEX.md header; add missing entries.
  2. Flag any refsrc/INDEX.md entry with no matching folder. </validate_existing>

<ask_for_reference_code step="2.3" type="HITL">

  1. Tell the user, briefly: the agent can't see code outside this repo — reference code (backend for a frontend repo, corporate/private libraries, a recently-changed public framework) lets it read without writing to it.
  2. Ask if there is reference code to add; if not, record no-op and stop.
  3. If yes, ask repo URL/path per codebase; guide: clone read-only into refsrc/<name>. </ask_for_reference_code>

<review_reference step="2.4">

  1. Confirm each newly cloned codebase sits under refsrc/<name> and stays read-only.
  2. Re-apply validate_existing checks (gitignore + refsrc/INDEX.md) for the new entries. </review_reference>

<validation_checklist>

  • .gitignore carries all three refsrc exceptions.
  • Every refsrc/* folder has a refsrc/INDEX.md entry, and vice versa.
  • User was asked about additional reference code. </validation_checklist>

</arrange_workspace_reference_source_code>

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. today First seen · 62 lines · 20 tokens per session scan A 542994b2fd31

Subscribe to this mod's changes

arrange-workspace-flow-reference-source-code is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 583 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.