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-reusegit 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-reuse)<a href="https://agentmods.dev/commands/griddynamics/rosetta/modernization-flow-reuse"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/modernization-flow-reuse.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.00017 | $0.00905 |
| Opus 5 | $0.00009 | $0.00452 |
| Sonnet 5 | $0.00003 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
modernization-flow-reuse 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernization Phase 1: Existing Library Analysis
Phase Flow
Phase 1: Existing Library Analysis
- Process each project separately
- Analyze code and tests
- Create reference-code-specs files
- Document interfaces and signatures
- Document business and tech purpose
- Analyze usage and visibility
- List unknowns and assumptions
- Link implementation and tests
- Describe test coverage
Context
PREREQUISITES: None
OBJECTIVES:
- Create complete, factual specification of existing code
- Understand functionality, requirements, edge cases, and usage
- Identify unknowns and create follow-up tasks
- Use and rely on performance optimizations already applied (we must not downgrade!).
- These project must not be modernized, but could be extended, and definitely must be reused!
Requirements
- MUST process each project separately
- MUST create
docs/reference-code-specs-<lib/project>.mdfor each project - MUST analyze ALL code AND associated unit tests
- MUST use search/grep/tools to discover all relevant details
- MUST document findings with evidence (references to actual code)
- MUST list all files and create todo tasks systematically
Address Edge Cases
Edge cases MUST be explicitly identified and documented:
- Case sensitivity handling
- Reference parameters and side effects
- Out parameters
- Null/undefined handling
- Boundary conditions
- Error conditions
Specification Contents (MANDATORY)
Each specification MUST include:
-
Interfaces & Method Signatures & Enums & Other Code Constructs
- Full signature with parameters, return types
- Access modifiers (public, private, internal, protected)
- Static vs instance
-
Business/Technology Purpose
- What does this code do?
- Why does it exist?
- What problem does it solve?
-
Special Requirements & Edge Cases
- Performance requirements
- Threading/concurrency considerations
- Transaction handling
- Security requirements
- Edge cases identified from tests
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 · 128 lines · 17 tokens per session scan A d0cc1e8d059a
modernization-flow-reuse is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 905 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.