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-testing)<a href="https://agentmods.dev/commands/griddynamics/rosetta/modernization-flow-testing"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/modernization-flow-testing/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-testing"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/modernization-flow-testing.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.01073 |
| Opus 5.5 | $0.00006 | $0.00429 |
| Sonnet 5.5 | $0.00003 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
modernization-flow-testing 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernization Phase 3: Test Coverage (OPTIONAL)
Phase Flow
Phase 3: Test Coverage (OPTIONAL - Execute only when explicitly requested)
- Complete Phase 2 first
- Analyze existing test coverage
- Identify gaps in test coverage
- Create unit tests for uncovered code
- Achieve 80% code coverage target
- Document test approach and coverage
- Integration tests are preferred
Context
PREREQUISITES: Complete Phase 2 (all original code specs created)
THIS PHASE IS OPTIONAL - Only execute when explicitly requested in the modernization context or by user.
OBJECTIVES:
- Establish baseline test coverage for original code before modernization
- Ensure original behavior is captured in tests for validation during migration
- Achieve 80% code coverage on original codebase
- Document existing behavior through comprehensive tests
- Provide safety net for modernization implementation
Requirements
- MUST process each project separately
- MUST analyze existing test coverage using coverage tools
- MUST identify code paths not covered by tests
- MUST create unit tests for uncovered code
- MUST achieve minimum 80% code coverage per project
- MUST document test approach in
docs/original-test-coverage-<lib/project>.md - MUST ensure tests validate actual behavior (not assumed behavior)
- MUST use existing tests as reference for style and patterns
- MUST create todo tasks for each test file or test suite
Test Creation Guidelines
Test Priorities
Focus on testing in this order:
- Public APIs - All public methods and interfaces
- Critical Business Logic - Core functionality and calculations
- Edge Cases - Boundary conditions, null handling, error conditions
- Integration Points - Service calls, database operations, external dependencies
Test Quality Requirements
- MUST test actual behavior (validate against running code where possible)
- MUST include edge cases identified in Phase 2 analysis
- MUST test error conditions and exception handling
- MUST test with realistic data
- MUST avoid brittle tests (don't over-specify implementation details)
- MUST follow existing test conventions and patterns
- SHOULD use descriptive test names explaining what is being tested
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 · 132 lines · 15 tokens per session scan A 278641903154
modernization-flow-testing is a command published in the GitHub repository griddynamics/rosetta (360 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 1,073 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
pm-tests
List missing unit-test companions for core/changed sources. Do not write tests into the business tree unless the user confirms.
loop
Your first output line MUST be: 🐙 Octopus Loop Mode.
write-unit-tests
Write meaningful unit tests for target code.
test
Execute comprehensive test suites (unit, integration, e2e) to validate implementation correctness and quality.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
generate-tests
Generate tests for changed files — unit tests for functions, integration tests for APIs, E2E for user flows.