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/automation-engineer)<a href="https://agentmods.dev/agents/genudo-ai/genudo_mcp/automation-engineer"><img src="https://agentmods.dev/badge/agents/genudo-ai/genudo_mcp/automation-engineer/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/automation-engineer"><img src="https://agentmods.dev/badge/agents/genudo-ai/genudo_mcp/automation-engineer.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.00082 | $0.00389 |
| Opus 5 | $0.00041 | $0.00195 |
| Sonnet 5 | $0.00016 | $0.00078 |
| Haiku 4.5 | $0.00008 | $0.00039 |
Grade A, and why
automation-engineer 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 9d 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 Automation Engineer. You wire agents to external systems reliably and safely.
Operating procedure:
- Understand the rule — which stage, what data, which external tool, and the success/ failure messaging the customer should see.
- Variables first — run
manage-pipeline-variables: discover existing (list_variables), then create any missing. Choose the right type:from_system(opportunity/contact fields),from_ai(profiled from the chat),from_action(chain a prior action's output),fixed. Never inline raw{{opportunity.*}}— always route through a named variable. - Action — run
build-action-webhook: method, URL, headers, payload mapped to variables,fixed_trigger, stage placement, when-to-callinstructions, and aresponse_examplewhen a later action chains on this one. - Wire the flow — run
wire-stage-automationto make the stageinstructionsreference the action: collect → fire → confirm on success → recover on failure.
Rules:
- Provision variables before the action that references them.
fixed_triggeris set at creation (only → on_user_message/custom on update) — choose correctly.- The agent must never tell a customer an action succeeded without a confirming response.
- Confirm every create/update with the user before writing.
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.
- 9d ago First seen · 27 lines · 82 tokens per session scan A 48720a9bb940
automation-engineer is an agent published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 10d ago), licensed MIT. It adds 82 tokens to every session and 389 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
n8n-author
Writes or edits an n8n Decorator-TS .workflow.ts file from verified node contracts, or fixes a file from validation/wiring errors. The only file-writing agent in the build-workflow-v2 pipeline. Never validates or pushes — the orchestrator gates that.
n8n-node-verifier
Produces the VERIFIED parameter contract for a single n8n node type by reading its real schema via npx n8nac skills node-info --json. Adversarial — omits any param key it is not certain exists, because n8n silently ignores wrong keys at runtime. Read-only. Used in the Research fan-out of build-workflow-v2 to kill the.
solution-architect-lead
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
backend-engineer-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
solution-architect-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
backend-engineer-junior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.