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-quick-fixgit 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-quick-fix)<a href="https://agentmods.dev/skills/macroman5/automationhelper_plugins/automation-quick-fix"><img src="https://agentmods.dev/badge/skills/macroman5/automationhelper_plugins/automation-quick-fix.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.00123 | $0.04682 |
| Opus 5 | $0.00062 | $0.02341 |
| Sonnet 5 | $0.00025 | $0.00936 |
| Haiku 4.5 | $0.00012 | $0.00468 |
Grade A, and why
automation-quick-fix 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 — 691 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Quick Fix
Fast-track resolver for common automation workflow error patterns across multiple platforms with immediate, proven solutions.
Supported Platforms
- Power Automate (Microsoft)
- n8n (Open-source)
- Make (formerly Integromat)
- Zapier
- Other JSON-based workflow platforms
Purpose
Provides rapid fixes for frequently encountered automation workflow errors across all platforms:
- Authentication errors (401/403)
- Throttling errors (429)
- Data format issues (JSON parsing, data transformation)
- Timeout errors
- Not found errors (404)
- Basic expression/formula errors
When to use this skill: Error matches a well-known pattern When to use automation-debugger instead: Unknown error, complex scenario, or quick fix doesn't resolve
Activation Triggers
Activates for messages like:
- "Quick fix for 429 error in SharePoint/API/webhook"
- "Fast solution for authentication error in n8n"
- "I'm getting throttled in Make, need immediate fix"
- "Parse JSON is failing in Zapier, quick help"
- "Function expects one parameter but was invoked with 2"
- "Unable to process template language expressions"
- "Fix this expression/filter/query/condition"
- User provides code snippet and asks for "quick fix" or "fix this"
- Status codes: 401, 403, 404, 429 with platform/connector context
- Platform-specific: "n8n node error", "Make scenario failing", "Power Automate action issue"
⚠️ IMPORTANT: Data Structure Check (NEW!)
Before applying any quick fix, quickly verify data structures in your flow:
Quick Data Type Check
// In filters/queries, check the where clause:
// Array of STRINGS (primitives):
"where": "@contains(item(), 'text')" // ← item() without property
// Array of OBJECTS:
"where": "@contains(item()?['Name'], 'text')" // ← item()?['Property']
If your flow has data structure mismatches (filter uses item() but loop uses items('Loop')?['Property']), this is NOT a quick fix scenario → use automation-debugger instead.
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 · 691 lines · 123 tokens per session scan A 49d4d7a6020d
automation-quick-fix is a skill published in the GitHub repository MacroMan5/AutomationHelper_plugins (3 stars, last pushed 10mo ago), licensed MIT. It adds 123 tokens to every session and 4,682 once invoked, about $0.0006 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-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…
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…
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…