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-review)<a href="https://agentmods.dev/commands/griddynamics/rosetta/modernization-flow-review"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/modernization-flow-review.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.1 | $0.00012 | $0.00576 |
| Opus 5 | $0.00006 | $0.00288 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
modernization-flow-review 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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernization Phase 7: Final Review
Phase Flow
Phase 7: Final Review
- Complete Phase 6 first
- Review all specs together
- Check pattern consistency
- Verify cross-project flows
- Cleanup final unknowns
- Request user clarifications
- Update all documentation
Context
PREREQUISITES: Complete Phase 6 (all target code specs created)
OBJECTIVES:
- Final consistency check across all target specs
- Ensure all inter-project dependencies accounted for
- Validate patterns are consistent
- Confirm all handoffs documented
- Validate migration / modernization priorities
Requirements
- MUST review ALL
docs/reference-code-specs-<lib/project>.mdfiles together - MUST review ALL
docs/original-code-specs-<lib/project>.mdfiles together - MUST review ALL
docs/target-code-specs-<lib/project>.mdfiles together - MUST review and update
docs/cross-project-analysis-<feature>.mdfile - MUST check for patterns and inconsistencies
- MUST verify cross-project flows are captured
- MUST update those files as necessary
- MUST NOT create any NEW files!
- MUST check assumptions and unknowns and cleanup those which are addressed (update respective parts of te original document and remove element completely from this section).
- MUST Request information from the user that is required for the modernization! Must not proceed if not properly addressed by the user! Remember this is the final check, any unknowns left will lead to problems!
Review Focus
-
Pattern Consistency
- Are similar problems solved similarly?
- Are patterns consistently applied?
-
Cross-Project Interactions
- All handoffs captured?
- All interfaces defined?
- All dependencies clear?
-
Completeness
- All edge cases addressed?
- All public APIs mapped?
- All service replacements defined?
Validation Checkpoint
MUST spawn separate subagent to validate grounding, truthfulness, gaps, consistency, reasoning, and overall completion of the phase.
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.
- 2d ago First seen · 75 lines · 12 tokens per session scan A 21d2fd54320f
modernization-flow-review is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 576 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
sdd-apply
Implement SDD tasks — writes code following specs and design.
sdd-status
Show structured SDD status for an active change.
sdd-verify
Validate implementation matches specs, design, and tasks.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
sdd-new
Start a new SDD change — runs exploration then creates a proposal.
sdd-onboard
Guided SDD walkthrough — onboard a user through the full SDD cycle using their real codebase.