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-validatorgit 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-validator)<a href="https://agentmods.dev/skills/macroman5/automationhelper_plugins/automation-validator"><img src="https://agentmods.dev/badge/skills/macroman5/automationhelper_plugins/automation-validator.svg" alt="Measured on agentmods" 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.00077 | $0.04386 |
| Opus 5 | $0.00039 | $0.02193 |
| Sonnet 5 | $0.00015 | $0.00877 |
| Haiku 4.5 | $0.00008 | $0.00439 |
Grade A, and why
automation-validator 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 6d 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 — 713 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Workflow Validator
Comprehensive pre-deployment validator for automation workflow JSON definitions across multiple platforms.
Supported Platforms
- Power Automate (Microsoft)
- n8n (Open-source)
- Make (formerly Integromat)
- Zapier
- Other JSON-based workflow platforms
Purpose
Validates automation workflows against:
- Syntax correctness - Valid JSON, proper structure
- Platform compliance - Schema, required fields, valid operations (platform-specific)
- Best practices - Error handling, performance, reliability
- Security - Hardcoded credentials, injection risks
- Documentation compliance - Connector/node limits, known constraints
When This Skill Activates
Triggers on:
- "Validate this workflow JSON"
- "Check this workflow JSON before deployment"
- "Review my workflow JSON for [platform]"
- "Is this flow ready to paste into Power Automate/n8n/Make?"
- "Validate my n8n workflow"
- "Lint this automation"
- "Pre-deployment check"
- Workflow JSON files - Any JSON with workflow/flow/automation context (examples: flow.json, workflow.json, scenario.json, automation.json, fixed_flow.json)
Validation Checklist
1. Syntax Validation
JSON Structure:
- Valid JSON syntax (balanced brackets, proper escaping)
- No trailing commas
- Proper string escaping for expressions
- No invalid characters
Power Automate Schema:
- Correct $schema URL
- Required root elements: definition, schemaVersion
- Parameters include $connections
- Valid contentVersion format
Structure:
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"contentVersion": "1.0.0.0",
"parameters": { /* Required */ },
"triggers": { /* Required */ },
"actions": { /* Required */ },
"outputs": {}
},
"schemaVersion": "1.0.0.0"
}
2. Triggers Validation
Required Fields:
- At least one trigger defined
- Trigger has "type" field
- Trigger has "inputs" object
- Valid trigger types: Request, Recurrence, ApiConnection, etc.
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.
- 6d ago First seen · 713 lines · 77 tokens per session scan A 264f47c7c8df
automation-validator is a skill published in the GitHub repository MacroMan5/AutomationHelper_plugins (3 stars, last pushed 10mo ago), licensed MIT. It adds 77 tokens to every session and 4,386 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 skills, from other repositories
calibration-diff
Compare the current Claude Code setup against the previous calibration run's baseline. Spawns only the evaluator (pass 2) — no planner, no calibrator, no edits. Useful between calibration runs (you manually edited a few files; what now shows resolved vs new?) and as a "did my changes hold up?" check after merging a…
calibration-doctor
Fast structural health check for a Claude Code setup. Detects broken config — JSON that doesn't parse, hook scripts that are missing or non-executable, subagent/skill files with malformed frontmatter, MCP servers whose command can't be found, and .gitignore that's missing .claude/calibration/. Prints a terse triage…
neural-add-bug
Manually log a bug into the neural memory knowledge graph when not using context log files. Links the bug node to the affected code by file path.
neural-inspect
Deep-dive into a specific code element — see its full context, callers, callees, siblings, and call chains in the knowledge graph.
calibrate-settings
Audits and tunes every settings.json Claude Code reads — user (/.claude/settings.json), user-local (/.claude/settings.local.json), project (.claude/settings.json), project-local (.claude/settings.local.json), and plugin-self when the project is itself a plugin. Flags committed secrets, --dangerously-skip-permissions…
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…