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-intake-legacygit 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-intake-legacy)<a href="https://agentmods.dev/skills/genudo-ai/genudo_mcp/migrate-intake-legacy"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/migrate-intake-legacy/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-intake-legacy"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/migrate-intake-legacy.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.00087 | $0.00460 |
| Opus 5 | $0.00044 | $0.00230 |
| Sonnet 5 | $0.00017 | $0.00092 |
| Haiku 4.5 | $0.00009 | $0.00046 |
Grade A, and why
migrate-intake-legacy 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 11d 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
Migrate: Intake Legacy Pipeline
Capture everything the old pipeline knows before any rewriting. This step is read-only — completeness beats tidiness; do not fix or re-style anything yet.
Sources (combine as available)
- Pasted text / files — old persona, global instructions, stage docs in any format.
- Live account — when the pipeline exists on the platform:
list_pipelines(persona + instructions + settings),list_pipeline_stages(per stage: name, nature, order, enter_condition, instructions, ai_persona),list_actions,list_variables, andget_stage_followupper stage.
Capture (the legacy spec)
Write ./genudo-migrate/<pipeline-slug>/legacy-spec.md with one section per item:
- Identity — pipeline name, channel, language, agent type, AI model if known.
- Persona — old persona text, verbatim.
- Global instructions — verbatim.
- Stages — per stage: name, nature, order, entry condition (or how entry was expressed in the old approach), in-stage instructions verbatim, data collected, opening message.
- Automations — actions with triggers, URLs, payload fields; variables with types.
- Follow-ups — per-stage schedules and drafting notes.
- Embedded business facts — pull out products, prices, policies, links, and named people found anywhere in the old text into their own list; these must survive migration verbatim.
Gaps
Mark anything missing or illegible as UNKNOWN — ask rather than guessing. Finish by listing
the open questions, then hand off to migrate-map-to-new. 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.
- 11d ago First seen · 37 lines · 87 tokens per session scan A fa0e0b29a508
migrate-intake-legacy is a skill published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 87 tokens to every session and 460 once invoked, about $0.0004 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.