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 MacroMan5/AutomationHelper_plugins --skill automation-build-flowgit clone --depth 1 https://github.com/MacroMan5/AutomationHelper_pluginsWrote 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/macroman5/automationhelper_plugins/automation-build-flow)<a href="https://agentmods.dev/skills/macroman5/automationhelper_plugins/automation-build-flow"><img src="https://agentmods.dev/badge/skills/macroman5/automationhelper_plugins/automation-build-flow/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/macroman5/automationhelper_plugins/automation-build-flow"><img src="https://agentmods.dev/badge/skills/macroman5/automationhelper_plugins/automation-build-flow.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.00099 | $0.04265 |
| Opus 5 | $0.00049 | $0.02132 |
| Sonnet 5 | $0.00020 | $0.00853 |
| Haiku 4.5 | $0.00010 | $0.00426 |
Grade A, and why
automation-build-flow 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.
How it starts
The opening of the file, as written. The whole thing — 755 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Build Flow
Professional workflow builder that generates complete, production-ready JSON for any automation platform.
Supported Platforms
- Power Automate (Microsoft)
- n8n (Open-source)
- Make (formerly Integromat)
- Zapier
- Other JSON-based workflow platforms
Purpose
This skill generates complete automation workflows by:
- Taking implementation plan or requirements as input
- Validating platform compatibility
- Using flow-builder sub-agent to generate complete JSON
- Ensuring all best practices are implemented
- Producing ready-to-import workflow JSON
When This Skill Activates
Automatically activates when user:
- Has implementation plan: "Build this workflow from the plan"
- Provides requirements: "Create a workflow that does X, Y, Z"
- Requests JSON generation: "Generate the flow JSON"
- Has plan from automation-brainstorm: "Use this plan to build the flow"
- Keywords: "build flow", "create workflow", "generate JSON", "implement this"
Prerequisites:
- Platform must be specified (or will ask)
- Requirements must be clear (or will request clarification)
Does NOT activate when:
- User needs help planning (use automation-brainstorm)
- User has error to debug (use automation-debugger)
- User wants validation only (use automation-validator)
Core Workflow
Phase 1: Input Analysis
-
Determine Input Type
Type A: Implementation Plan (from automation-brainstorm)
- Structured markdown plan
- Contains all sections (trigger, actions, error handling, etc.)
- Platform specified
- Ready to build → Proceed to Phase 2
Type B: Direct Requirements (user provided)
- User describes what they want
- May be less structured
- Needs clarification → Gather requirements
-
Verify Platform
Check if platform specified:
- In plan: Check "Platform" section
- In message: Look for platform mention
- If missing: Ask using AskUserQuestion
Use AskUserQuestion tool: Question: "Which platform should I generate this workflow for?" Header: "Platform" Options: - Power Automate (Microsoft, generates .json for "Paste code" feature) - n8n (Open-source, generates workflow.json for import) - Make (Integromat, generates scenario blueprint.json) - Zapier (Generates zap JSON for import API) - Other (Specify platform and format needed)
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 · 755 lines · 99 tokens per session scan A b91d0d4e8645
automation-build-flow is a skill published in the GitHub repository MacroMan5/AutomationHelper_plugins (3 stars, last pushed 10mo ago), licensed MIT. It adds 99 tokens to every session and 4,265 once invoked, about $0.0005 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 skills, from other repositories
deploy-setup
Wire up a freshly scaffolded Starter Series project for its first release — detect the template, register required GitHub secrets, set up OIDC trusted publishing where applicable, and trigger the first CD run. Pairs with the create skill (you scaffold first, then run this).
create
Scaffold a new project from the Starter Series templates (MCP server, Discord/Telegram bot, VS Code / browser extension, Electron, React Native, Cloudflare Pages, npm package, Docker deploy).
calibration-onboarding
First-time setup guide for claude-calibration and Claude Code config in general. Detects what config the project already has (CLAUDE.md, .claude/, settings.json, hooks, agents, skills, .mcp.json), names the minimal viable additions for this project's stack, and bridges into /claude-calibration:calibration-doctor…
calibration
Discovery-friendly dispatcher above /calibrate. With no args, prints a menu of every calibration flow — the three /calibrate built-in modes (tighten / harden / cost), the two standalone convenience flows (audit, diff), and the per-feature shortcuts (skills / subagents / claude-md / rules / settings / hooks / mcp /…
calibrate-plugins
Audits installed plugins, registered marketplaces, and (when the project itself is a plugin) the local manifest at .claude-plugin/plugin.json. Flags manifests missing name or version, manifests that don't parse, components misplaced under .claude-plugin/ instead of at the plugin root, plugins that use legacy commands/…
calibration-flow
Evaluate the BEHAVIOUR of a multi-step workflow, not static config: does the chain deliver intent, and are its agent→agent / agent→skill handoffs sound? Drives a named workflow over a case set of golden fixtures (each /{input/,expected.md}), diffs what it finds against the oracle, and scores node recall/precision…