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 skills add genudo-ai/genudo_mcp --skill migrate-map-to-newgit 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/skills/genudo-ai/genudo_mcp/migrate-map-to-new)<a href="https://agentmods.dev/skills/genudo-ai/genudo_mcp/migrate-map-to-new"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/migrate-map-to-new/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/skills/genudo-ai/genudo_mcp/migrate-map-to-new"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/migrate-map-to-new.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.00094 | $0.00605 |
| Opus 5 | $0.00047 | $0.00302 |
| Sonnet 5 | $0.00019 | $0.00121 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
migrate-map-to-new 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 12d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate: Map Legacy to New Approach
Re-author the legacy spec against the current templates. The current approach IS the spec:
the instruction-guides skill (templates + rules) plus the author-pipeline-brain and
author-stages rubrics. Never paste legacy text into new fields unchanged.
Steps
- Run the
instruction-guidesskill; load./genudo-migrate/<pipeline-slug>/legacy-spec.md. - Persona + global instructions — re-author per
author-pipeline-brain: identity and voice into the persona; cross-stage behaviour, grounding, style, and escalation into the global instructions. Old stage-level text that is really global (repeated safety lines, generic tone rules) moves UP into the global layer — and is deleted from every stage. - Stages — re-author per
author-stages. Map old stages onto a clean journey: split stages that mixed two jobs, merge duplicates, and express entry as observableenter_conditionsignals. Per stage: 3–6 compact flow steps, required data, exit, nature, order, short name. Old "when to move" prose becomes the NEXT stage'senter_condition. - Automations & follow-ups — carry actions, variables, and follow-up schedules over into the new stage layout; where a stage split or merged, decide which new stage owns each.
- Business facts — every fact from the legacy spec's facts list must appear in the new
spec (global instructions, a stage flow, or a knowledge table via
manage-knowledge-base). Tick them off one by one.
Output
./genudo-migrate/<pipeline-slug>/new-spec.md— the full new-approach pipeline, in the same shapeprovision-pipelineconsumes../genudo-migrate/<pipeline-slug>/mapping.md— a table: legacy item → destination (kept / moved to X / merged into Y / dropped — why) plus open questions for the user.
Review both with the user; every drop needs an explicit yes. Then apply: provision-pipeline
(new pipeline, default) or edit-pipeline-instructions + update_stage (in place, only when
the user names the target). No account writes here.
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.
- 12d ago First seen · 39 lines · 94 tokens per session scan A 571576066bb6
migrate-map-to-new is a skill published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 94 tokens to every session and 605 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
comfyui-skill-openclaw
Run registered ComfyUI workflows through the fast comfyui-skill CLI, and use the official local Comfy MCP for live template, node, model, validation, and orchestration capabilities. Use this Skill when: (1) The user requests to "generate an image", "draw a picture", or "execute a ComfyUI workflow". (2) The user has…
superloopy-loop
Use Superloopy's lightweight strict-evidence loop for Codex tasks that need durable progress, criteria, and artifact-backed completion.
deepline-ads-audiences
Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal…
deepline-pre-research
Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or…
niche-signal-discovery
Discover niche first-party signals that differentiate Closed Won vs Closed Lost accounts for ICP analysis. Use when the user provides won/lost customer domain lists and wants differential signals (website content, job listings, tech stack, maturity markers) to build account scoring models and prospecting criteria.…
deepline-engine
Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot. Invoke this skill explicitly when the user asks to build an engine.