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/modernization-flow-mappinggit 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-mapping)<a href="https://agentmods.dev/commands/griddynamics/rosetta/modernization-flow-mapping"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/modernization-flow-mapping.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.00014 | $0.01229 |
| Opus 5 | $0.00007 | $0.00615 |
| Sonnet 5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00001 | $0.00123 |
Grade A, and why
modernization-flow-mapping 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernization Phase 6: Implementation Mapping
Phase Flow
Phase 6: Implementation Mapping
- Complete Phase 5 first
- Define technical approaches
- Compare multiple alternatives
- Map source to target
- Identify supporting libraries
- Address edge cases
- Ensure backward compatibility
- Create target-code-specs files
- Emphasize port file-by-file
Context
PREREQUISITES: Complete Phase 5 (cross-project analysis)
OBJECTIVES:
- Define technical approaches for modernization
- Identify and compare multiple options (especially with edge cases)
- Map source code to target code
- Identify supporting libraries and packages
- Address all edge cases and special requirements
- Identify at least three alternatives (in memory)
- Validate backward compatibility and overall modernization goals instead of just modern best practices, think about side affects, reason WHY did you choose one alternative (in memory)
- Validate your alternative vs existing code (in memory)
- Document only selected alternative, reasons, side affects, and very briefly the other alternatives reviewed
- Design principle: backward compatibility (names, signature, behavior) and less code is better
- In case of strong cases of idiomatic target make sure to have two implementations: compatible non-idiomatic and idiomatic new (examples: original enumerator methods and normal IEnumerable implementation, original methods with refs/outs and new methods, original methods and new properties, new async methods)
- YOU MUST EMPHASIS IN THE OUTPUT DOCUMENT:
- Backward compatibility is a MUST, additional ctor/fields/properties/methods/classes/enums are allowed.
- To PORT code file-by-file, class by class, method by method, re-read-source-write-target one-by-one. Do not reinvent! Require creation of todo tasks.
- To PORT tests! Test by test, re-read-source-write-target one-by-one! Require creation of todo tasks.
- To VALIDATE all tests and code from target matching the source (logic and contract).
- YOU MUST STRESS IN THE OUTPUT DOCUMENT:
- To perform code and tests file-by-file comparison source vs target of original and implemented contract and logic, until there are no gaps and inconsistencies, re-read both source and target.
- To perform EXACT behavior copy, excluding async and enumerators.
- To put mapping which file to match to which file.
- To implement async and enumerators.
- To update
docs/target-code-specs-<lib/project>.mdto match ACTUAL implementation with actual contracts, paths, API, async, additional methods/properties, enumerables implemented AS IF it was planned so good (DO NOT: create new sections, green checkboxes, "implemented" statuses, and so on).
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 · 127 lines · 14 tokens per session scan A b9a0f1634e76
modernization-flow-mapping is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 1,229 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.