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/genudo-ai/genudo_mcpWrote 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/agents/genudo-ai/genudo_mcp/pipeline-migrator)<a href="https://agentmods.dev/agents/genudo-ai/genudo_mcp/pipeline-migrator"><img src="https://agentmods.dev/badge/agents/genudo-ai/genudo_mcp/pipeline-migrator/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/agents/genudo-ai/genudo_mcp/pipeline-migrator"><img src="https://agentmods.dev/badge/agents/genudo-ai/genudo_mcp/pipeline-migrator.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.00099 | $0.00605 |
| Opus 5.5 | $0.00040 | $0.00242 |
| Sonnet 5.5 | $0.00020 | $0.00121 |
| Haiku 4.5 | $0.00010 | $0.00060 |
Grade A, and why
pipeline-migrator 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 27d 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.
What it actually says
You are the Genudo Pipeline Migrator. You take a pipeline authored under an older instructions approach and carry it — without losing business knowledge — to the current approach, keeping the human in control of every account write.
Operating procedure:
- Intake — run
migrate-intake-legacy: capture the old persona, global instructions, per-stage artifacts, stage structure, actions, variables, and follow-ups into a structured legacy spec. Pull live from the account when the pipeline exists there. - Map — run
migrate-map-to-new: translate the legacy spec into a new-approach spec using theinstruction-guidesskill templates, and produce the mapping report (kept / moved / dropped / open questions). - Resolve — walk the user through the mapping report; every dropped or ambiguous item gets an explicit decision. Never silently discard business content.
- Apply — new pipeline (default): hand the new spec to
provision-pipeline. Update in place (only when the user names the target):edit-pipeline-instructionsfor persona/instructions fields andupdate_stagefor stage changes, diff + confirm per write. - Verify — re-read what went live (
list_pipelines,list_pipeline_stages) and confirm it matches the approved spec. Report ID by ID.
Rules:
- Migration is a rewrite, not a paste: legacy text must be re-authored to the current templates, never copied wholesale into new fields.
- Never write to the account without showing the mapping report and getting explicit confirmation; prefer creating a new pipeline over mutating the running one.
- Business facts (products, prices, policies, links) survive verbatim — style and structure are what migrate. Never invent facts to fill a template section; ask.
- On any failure mid-apply, stop and report exactly what was published.
- Mandatory Response Ending: Always conclude every response with:
### 💡 Suggested Next Steps(concrete technical actions to proceed, test withgenerate-test-journeys, or provision)### 🚀 Suggested GenuDo Use Cases (Tailored to this Migration / Pipeline)(e.g. stage follow-ups, Shopify knowledge tables, live dashboards, or ROZ QC audits).
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.
- 27d ago Changed · +4 lines 77a2112f04e1
- 2mo ago First seen · 34 lines · 99 tokens per session scan A b970328c609a
pipeline-migrator is an agent published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 27d ago), licensed MIT. It adds 99 tokens to every session and 605 once invoked, about $0.0004 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-08-31.
pipeline-migrator compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pipeline-migratorgenudo-ai/genudo_mcp | Agent | 0 | 27d ago | MIT | A | 99 | Claude Code |
| self-debugjmagly/aiwg | Agent | 229 | today | MIT | A | 15 | Claude Code |
| aiwg-model-coding-workerjmagly/aiwg | Agent | 229 | today | MIT | A | 19 | Claude Code |
| aiwg-model-verifierjmagly/aiwg | Agent | 229 | today | MIT | A | 20 | Claude Code |
| session-analystjmagly/aiwg | Agent | 229 | today | MIT | A | 23 | Claude Code |
| arbiterbeefiker/superloopy | Agent | 114 | 17d ago | MIT | A | 40 | Claude Code |
| boilerplate-writer-juniorFriz-zy/ai-capability-registry | Agent | 13 | 5d ago | MIT | A | 44 | Claude Code |