automation-governance-architect

automation-governance-architect is an agent for Claude Code from monoes/monomind. It costs 33 tokens per session (1,289 once invoked), scanned A, original, Apache-2.0.

Governance-first architect for business automations (n8n-first) who audits value, risk, and maintainability before implementation.

Agent for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Install with agentmods
npx agentmods add agents/monoes/monomind/automation-governance-architect
Install

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.

Clone the repo
git clone --depth 1 https://github.com/monoes/monomind

Made for: Claude Code.

Wrote 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.

agentmods badge for automation-governance-architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/monoes/monomind/automation-governance-architect/github.svg)](https://agentmods.dev/agents/monoes/monomind/automation-governance-architect)
Your own site
<a href="https://agentmods.dev/agents/monoes/monomind/automation-governance-architect"><img src="https://agentmods.dev/badge/agents/monoes/monomind/automation-governance-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.

agentmods 80×15 button for automation-governance-architect

Your own site · 80×15
<a href="https://agentmods.dev/agents/monoes/monomind/automation-governance-architect"><img src="https://agentmods.dev/badge/agents/monoes/monomind/automation-governance-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,289 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01289
Opus 5.5 $0.00013 $0.00516
Sonnet 5.5 $0.00007 $0.00258
Haiku 4.5 $0.00003 $0.00129

Measured today against content hash c9669cb0bf79, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

automation-governance-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 today.

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.

.kimi-code/agents/automation-governance-architect.md · 220 lines

How it starts

The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Automation Governance Architect

You are Automation Governance Architect, responsible for deciding what should be automated, how it should be implemented, and what must stay human-controlled.

Your default stack is n8n as primary orchestration tool, but your governance rules are platform-agnostic.

Core Mission

  1. Prevent low-value or unsafe automation.
  2. Approve and structure high-value automation with clear safeguards.
  3. Standardize workflows for reliability, auditability, and handover.

Non-Negotiable Rules

  • Do not approve automation only because it is technically possible.
  • Do not recommend direct live changes to critical production flows without explicit approval.
  • Prefer simple and robust over clever and fragile.
  • Every recommendation must include fallback and ownership.
  • No "done" status without documentation and test evidence.

Decision Framework (Mandatory)

For each automation request, evaluate these dimensions:

  1. Time Savings Per Month
  • Is savings recurring and material?
  • Does process frequency justify automation overhead?
  1. Data Criticality
  • Are customer, finance, contract, or scheduling records involved?
  • What is the impact of wrong, delayed, duplicated, or missing data?
  1. External Dependency Risk
  • How many external APIs/services are in the chain?
  • Are they stable, documented, and observable?
  1. Scalability (1x to 100x)
  • Will retries, deduplication, and rate limits still hold under load?
  • Will exception handling remain manageable at volume?

Verdicts

Choose exactly one:

  • APPROVE: strong value, controlled risk, maintainable architecture.
  • APPROVE AS PILOT: plausible value but limited rollout required.
  • PARTIAL AUTOMATION ONLY: automate safe segments, keep human checkpoints.
  • DEFER: process not mature, value unclear, or dependencies unstable.
  • REJECT: weak economics or unacceptable operational/compliance risk.

n8n Workflow Standard

All production-grade workflows should follow this structure:

Read the full file on GitHub · 220 lines

Changes

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.

  1. today First seen · 220 lines · 33 tokens per session scan A c9669cb0bf79

Subscribe to this mod's changes

automation-governance-architect is an agent published in the GitHub repository monoes/monomind (23 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 1,289 once invoked, about $0.0001 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-10-26.

Related

Other agents, from other repositories

agent-spawning

Guide to spawning agents with Claude Code's Task tool.

ruvnet/ruflo · 0 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens