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 pipeline-managementgit 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/pipeline-management)<a href="https://agentmods.dev/skills/genudo-ai/genudo_mcp/pipeline-management"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/pipeline-management/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/pipeline-management"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/pipeline-management.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.00045 | $0.00770 |
| Opus 5.5 | $0.00018 | $0.00308 |
| Sonnet 5.5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
genudo-pipeline-management 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 22d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GenuDo Pipeline Management
Overview
Guidelines and multi-step runbook for creating, modifying, and troubleshooting conversational automation pipelines, stages, and action bindings via GenuDo MCP tools.
Key Tools
| Purpose | MCP Tool |
|---|---|
| Fetch available pipelines | list_pipelines |
| Inspect stages of a pipeline | list_pipeline_stages |
| Read valid build choices (models, channels) | get_pipeline_options |
| Scaffold a new pipeline | create_pipeline |
| Add a stage to a pipeline | create_stage |
| Attach actions/webhooks to a stage | create_action |
| Manage custom variables | create_variable, list_variables, update_variable |
| Update live pipeline / stages | update_pipeline, update_stage, update_action |
| Enroll contact into a pipeline | start_pipeline_journey |
Step-by-Step Workflow
1. Discovery First
Always check what already exists before creating new objects:
- Call
list_pipelinesto check existing pipelines and their IDs. - Call
list_pipeline_stageswithpipeline_idto inspect current stages, order, instructions, andenter_conditionrules. - Call
get_pipeline_optionsto retrieve allowed models, channel types (WhatsApp, Messenger, Instagram, Web), and system capabilities.
2. Pipeline Scaffolding
When creating a pipeline (create_pipeline):
- Provide a clear
nameindicating business role (e.g., "Inbound Sales Qualifying - WhatsApp"). - Define global
instructions(business hours, company persona, tone, escalation triggers). - Configure the default AI model and connected communication channel.
3. Stage Architecture
When creating stages (create_stage):
- Logical Flow: Order stages chronologically (e.g.,
Greeting / Discovery→Qualification→Booking / Handoff→Closed Won / Lost). - Enter Conditions: Define unambiguous enter conditions so the AI transitions at the right conversation milestone.
- Stage Instructions: Focus on the specific objective of that stage (e.g., "Collect user budget and project timeline").
- Opening Messages: Specify whether the stage should send an opening message or wait for customer input.
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.
- 22d ago First seen · 68 lines · 45 tokens per session scan A 224dc3f71b1d
genudo-pipeline-management is a skill published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 770 once invoked, about $0.0002 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-09-25.
Other skills, from other repositories
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
workspace-prune-working
Clean up .aiwg/working/ by promoting, archiving, or deleting temporary files.
workspace-realign
Reorganize and update .aiwg/ documentation to reflect current project reality.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
index
Build, query, inspect dependencies, sync Fortemi Core cache, and report status for the searchable index of SDLC artifacts in .aiwg/.