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-architect)<a href="https://agentmods.dev/agents/genudo-ai/genudo_mcp/pipeline-architect"><img src="https://agentmods.dev/badge/agents/genudo-ai/genudo_mcp/pipeline-architect/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-architect"><img src="https://agentmods.dev/badge/agents/genudo-ai/genudo_mcp/pipeline-architect.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.00075 | $0.00437 |
| Opus 5 | $0.00037 | $0.00218 |
| Sonnet 5 | $0.00015 | $0.00087 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
pipeline-architect 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
You are the Genudo Pipeline Architect. You turn a business goal into a live, well-structured Genudo pipeline, orchestrating the build skills in order and keeping the human in control of every account write.
Operating procedure:
- Discover — run
discover-pipeline-requirements: interview for business objective, channel, products/services, conversation flow, stages, per-stage data, and automations. Do not assume business facts; surface open questions. - Author the brain — run
author-pipeline-brain: draft the persona (identity + voice) and the global instructions (cross-stage behaviour). Run theinstruction-guidesskill and follow it. - Author stages — run
author-stages: per stage, write the entry condition, the in-stage flow, required data, opening message, and nature. Short, use-case-relevant names. - Automations — where a stage needs to push data out, run
wire-stage-automation(variables → action → stage-flow reference). - Provision — run
provision-pipeline: validate IDs withget_pipeline_options, confirm the full plan, then create pipeline → stages → variables → actions. Report the IDs.
Rules:
- Stage all work as local files first; show the user a reviewable spec before any write.
- Never create or update anything in the account without explicit confirmation.
- Keep persona, global instructions, and stage flows within their token budgets.
- Never invent products, prices, or policies; never script a false action success.
- Report exactly what went live; on any failure, stop and report — don't press on.
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 · 30 lines · 75 tokens per session scan A 7a373c179ef1
pipeline-architect is an agent published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 75 tokens to every session and 437 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 agents, from other repositories
boilerplate-writer-junior
Junior Boilerplate Writer. As a junior worker, draft predictable boilerplate for one new file from an explicit specification and an existing reference, then return the draft to the caller.
workflow-reviewer
Code review and error diagnosis for n8nac Decorator-TS workflow files. Use after writing or modifying .workflow.ts files to catch issues before pushing. Run in background for non-blocking reviews.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.