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/modernization-flow-grouping)<a href="https://agentmods.dev/commands/griddynamics/rosetta/modernization-flow-grouping"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/modernization-flow-grouping/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/modernization-flow-grouping"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/modernization-flow-grouping.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.00015 | $0.00658 |
| Opus 5.5 | $0.00006 | $0.00263 |
| Sonnet 5.5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
modernization-flow-grouping 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernization Phase 4: Class Group Analysis
Phase Flow
Phase 4: Class Group Analysis
- Complete Phase 2 (or Phase 3 if executed) first
- Identify tightly-coupled classes
- Define bounded contexts
- Map flows between groups
- Trace dependencies deeply
- Update original-code-specs files
Context
PREREQUISITES: Complete Phase 2 (all original code specs created), and Phase 3 if executed
OBJECTIVES:
- Identify tightly-coupled classes (bounded contexts)
- Map flows between class groups
- Trace dependencies deep (2-3 levels minimum)
- Connect cross class group flows
Requirements
- MUST treat each output file as a SEPARATE TASK
- MUST process each project separately
- MUST update the same
docs/original-code-specs-<lib/project>.mdfile (append to existing) - MUST place class group definitions at the top of the file
Define Class Groups
IMPORTANT: A class group is a collection of tightly-coupled classes that work together within a single project to provide a cohesive capability. Class groups are identified within bounded contexts and represent classes that:
- Share data or state (technical coupling)
- Provide related business functionality (business cohesion)
- Have frequent interactions and dependencies
- Form a natural unit within the project structure
For each class group, document:
- Name: Descriptive name for the class group
- Classes: List all classes in the group
- Purpose: What business/technical capability does this group provide?
- Boundaries: What defines the boundary of this group?
- Internal Cohesion: How are classes coupled within the group?
Map Flows
- MUST map flows between class groups
- MUST trace at least 2-3 steps deep
- MUST connect cross class group flows
- MUST identify dependencies and call chains
- MUST document flow direction and data passed
Evidence Required
- MUST reference all findings with evidence
- MUST provide grep/search results
- MUST include file paths and line numbers
- MUST show actual code references
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 · 81 lines · 15 tokens per session scan A f03d6e836529
modernization-flow-grouping is a command published in the GitHub repository griddynamics/rosetta (363 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 658 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
superskill
route a task through superskill packs.
deploy-check
Pre-flight verification before pushing to main. Reproduces the CI gates locally so the push doesn't fail in production.
xpoz-best-practices
Reference docs for Xpoz query syntax, pagination, field selection, platform tools, and authentication. Usage: /xpoz-best-practices.
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.