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 discover-pipeline-requirementsgit 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/discover-pipeline-requirements)<a href="https://agentmods.dev/skills/genudo-ai/genudo_mcp/discover-pipeline-requirements"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/discover-pipeline-requirements/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/discover-pipeline-requirements"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/discover-pipeline-requirements.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.00109 | $0.00559 |
| Opus 5 | $0.00055 | $0.00280 |
| Sonnet 5 | $0.00022 | $0.00112 |
| Haiku 4.5 | $0.00011 | $0.00056 |
Grade A, and why
discover-pipeline-requirements 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.
What it actually says
Discover Pipeline Requirements
Turn a vague "I want a WhatsApp agent" into a complete, buildable spec. Ask, don't assume. This skill only gathers and writes a local spec — it never touches the account.
Interview (one topic at a time, conversational)
Ask in this order; skip anything the user already gave. Reflect answers back briefly.
- Business objective — what is this pipeline for, and what counts as a win? e.g. "Onboard WhatsApp leads, recommend a course, register interested leads to a Google Sheet."
- Channel — WhatsApp, Messenger, Instagram, or LinkedIn? (Confirm valid options with
get_pipeline_options.) - Products / services — what are they selling, and the key details (names, who it's for, prices if stable, differentiators)? This makes the agent product-aware.
- Conversation flow — walk the journey: how should it welcome, then qualify, then propose, then close? What happens first, what comes next?
- Stages — from the flow, propose stage names (1–2 words, use-case relevant, e.g.
Welcome,Qualify,Recommend,Register). Confirm the set and order. - Required data per stage — what must be collected, especially in the closing/registration stage (e.g. name, phone, course).
- Automations — which stage should fire what, and what data goes to which tool (Zapier / Make / n8n / Google Sheets / CRM)?
Then surface open questions, assumptions, and conflicts — don't guess business facts.
Output
Write the brief to <workdir>/genudo-build/<pipeline-slug>/spec.md with sections matching the 7 topics
above, plus open-questions.md. Slugify the objective into a short pipeline name.
(No filesystem? Keep the spec inline in the conversation.)
Confirm the spec proposal with the user before anyone moves on to authoring. When approved,
hand off to author-pipeline-brain.
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 · 40 lines · 109 tokens per session scan A 20fb06782229
discover-pipeline-requirements is a skill published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 109 tokens to every session and 559 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.