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-implementgit 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-implement)<a href="https://agentmods.dev/commands/griddynamics/rosetta/modernization-flow-implement"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/modernization-flow-implement.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.00013 | $0.01064 |
| Opus 5 | $0.00006 | $0.00532 |
| Sonnet 5 | $0.00003 | $0.00213 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
modernization-flow-implement 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 yesterday.
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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernization Implementation Phase
Context
PREREQUISITES:
- Complete Phase 7 (final cross-project review)
- EXPLICIT HUMAN APPROVAL of all target specs
Requirements
- MUST follow approved target specifications
- MUST implement one project at a time (or per approved plan)
- MUST maintain backward compatibility for public APIs
- MUST write tests based on original code understanding
- MUST validate against original specs
- MUST achieve 80% minimum code coverage per project
- MUST USE FLOW
coding-flow.mdfor actual implementation
DOs AND DON'Ts FOR MODERNIZATION
DO:
- ✅ DO analyze thoroughly before proposing changes
- ✅ DO document all findings with evidence
- ✅ DO call out unknowns and assumptions explicitly
- ✅ DO create follow-up tasks for ambiguities
- ✅ DO process each phase completely before moving to next
- ✅ DO validate completeness at each checkpoint
- ✅ DO maintain public API compatibility (or document changes)
- ✅ DO adopt modern features where appropriate
- ✅ DO leverage standard libraries and established packages
- ✅ DO write comprehensive tests based on original behavior
DON'T:
- ❌ DON'T skip phases or rush through analysis
- ❌ DON'T generalize or assume - document facts only
- ❌ DON'T provide code in specs - use interfaces and signatures
- ❌ DON'T suggest solutions during analysis phase
- ❌ DON'T break public APIs without explicit approval
- ❌ DON'T implement before specs are approved
- ❌ DON'T change requirements without approval
- ❌ DON'T ignore edge cases from original code
- ❌ DON'T simplify functionality without approval
EMPHASIS ON CRITICAL RULES
THESE RULES ARE COMMONLY IGNORED - PAY ATTENTION
- NO CODE IN SPECS - Use interfaces and method signatures only, NOT implementation code
- NO GENERALIZATION - Document facts only, not patterns or abstractions
- NO ASSUMPTIONS - Call out all assumptions explicitly
- EVIDENCE REQUIRED - All findings must reference actual code
- COMPLETE EACH PHASE - Do not skip or rush through phases
- VALIDATE CHECKPOINTS - Verify completeness before proceeding
- PUBLIC API COMPATIBILITY - Maintain or explicitly document changes
- PROCESS SEPARATELY - Each project is its own task
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.
- yesterday First seen · 129 lines · 13 tokens per session scan A 92128bf41abd
modernization-flow-implement is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 1,064 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.
xpoz-best-practices
Reference docs for Xpoz query syntax, pagination, field selection, platform tools, and authentication. Usage: /xpoz-best-practices.
align
Verify spec-vs-spec alignment and brevity across the intent tree. This is NOT QA — QA checks code against a spec; alignment checks whether specs are consistent with their ancestors and internally tight against the Brevity Contract. The aligner runs three passes per walk.
deploy-check
Pre-flight verification before pushing to main. Reproduces the CI gates locally so the push doesn't fail in production.
validate-fix
Validate a proposed React fix with React-Sentinel assertions or replay checks.
rclone_mkdir
Make the path if it doesn't already exist.