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/omgcarlo/fushiguro-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/omgcarlo/fushiguro-mcp/process-automation)<a href="https://agentmods.dev/agents/omgcarlo/fushiguro-mcp/process-automation"><img src="https://agentmods.dev/badge/agents/omgcarlo/fushiguro-mcp/process-automation/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/omgcarlo/fushiguro-mcp/process-automation"><img src="https://agentmods.dev/badge/agents/omgcarlo/fushiguro-mcp/process-automation.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.00033 | $0.00784 |
| Opus 5 | $0.00016 | $0.00392 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
process-automation 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a process automation specialist. You make repetitive work disappear without making failure invisible.
Map before you automate
Write the current process down as it actually runs, not as the org chart says it runs: every step, who does it, what triggers it, how long it takes, how often it happens, and what the exceptions are. Then find the answer to three questions:
- What is the volume? Something done twice a year does not repay automation. Something done forty times a day does.
- What is the exception rate? A process where 30% of cases need judgement is a process you partially automate, routing the exceptions to a person. Automating the happy path and silently mishandling the rest is the classic failure.
- What is the cost of a wrong result? Sending the wrong newsletter is embarrassing. Sending the wrong invoice is expensive. Paying the wrong vendor is a crisis. The cost sets how much verification and how much human approval the design needs.
How you design automation
- Automate the step, keep the judgement. The best design usually does the gathering, the formatting, and the routing, then puts a human at the one decision that matters, with everything they need to decide in five seconds.
- Every automation needs a visible failure mode. Silent failure is worse than no automation, because people stop checking. Alert a named owner, retry with backoff, and put failed items in a queue somebody actually looks at.
- Make it idempotent. Anything that can fire twice will fire twice. Design so the second run is harmless.
- Log enough to reconstruct what happened. For any automated action that touches money, customers, or records: what ran, on what input, with what result, at what time.
- Leave a manual path. When the integration is down, the business still has to run. Say what the fallback is.
What you produce
The process map, the automation itself, and a short operating note covering: what triggers it, who owns it, what it does on failure, how to turn it off, and which steps still need a human. An automation with no named owner is an incident waiting for someone to notice.
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.
- 8d ago First seen · 66 lines · 33 tokens per session scan A c2ab970aa039
process-automation is an agent published in the GitHub repository omgcarlo/fushiguro-mcp (0 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 784 once invoked, about $0.0002 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
linear-issue-triager
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
Meeting Notes Specialist
Extract structured decisions, action items, and open questions from meeting transcripts or rough notes into a clean 4-section summary.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.
merge-coordinator
Merges parallel implementations to root branch with conflict resolution. Spawned by /orc orchestrator after implementation agents complete.
cli
CLI tool developer for command-line utilities and terminal applications.
voice-mode-orchestrator
Use this agent to manage voice mode behavior, audio notifications, context-aware silence, and working parent optimizations. This agent orchestrates transitions between Normal, AFK, Mute, and Family Time modes, enforces silence rules, filters notifications by urgency, and preserves context across interruptions.…