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/external-lib-flowgit 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/external-lib-flow)<a href="https://agentmods.dev/commands/griddynamics/rosetta/external-lib-flow"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/external-lib-flow.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.00020 | $0.01493 |
| Opus 5 | $0.00010 | $0.00746 |
| Sonnet 5 | $0.00004 | $0.00299 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
external-lib-flow 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Routine - Execute sequentially - Use Todo Tasks
Context
- Purpose: Onboard AI to external codebase for usage understanding
- Tool: Repomix (MCP or CLI) to package codebase (compressed XML)
- Target: Two documents in refsrc folder and in Rosetta
- File:
{project-name}.xml(compressed codebase, unmodified Repomix output) - File:
{project-name}-onboarding.md(brief Learning Flow with reference)
- File:
- Files involved: Project path, README, package files for auto-detection
- MUST generate brief Learning Flow (3-5 words per step, max 20 lines)
- MUST use compressed XML (Tree-sitter) for small output
- Onboarding document MUST specify KB title and search instructions
- Update ARCHITECTURE.md based on template
MUST use refsrc/{project-name}.xml and refsrc/{project-name}-onboarding.md. MUST use grep or search with those, because those are big files.. Combine this rule for multiple external dependencies. - Workflow state MUST be saved to
agents/TEMP/<FEATURE>/external-lib-flow-state.mdfile.
Onboarding Flow
Phase 0: Prerequsites
- All Rosetta prep steps MUST be FULLY completed
- USE SKILL
load-project-context,orchestration,hitl - MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
Phase 1: Discovery
- Ask project path
- Auto-detect project name
- Auto-detect version number
- Auto-detect tech stack
Phase 2: Analysis
- Package with compression enabled
- Analyze README for usage
- Extract main entry points
- Generate Learning Flow summary
Phase 3: Publishing
- Upload compressed XML as-is
- Create brief onboarding document
- Confirm both document IDs
- Cleanup temporary files
Phase 4: Verification
- Search by project name
- Verify tags present
- Display Learning Flow
- Confirm AI onboarded
Make sure to have todo tasks for each step! Do not skip steps!
Phase 1: Discovery
Idea
Ask or confirm user for project path with helpful suggestions. Auto-detect all metadata from project files to minimize user questions.
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 · 163 lines · 20 tokens per session scan A 3d489d0dbbdb
external-lib-flow is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 1,493 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
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
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.