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 agentmods add agents/eco-ansible-content/agentic-workflows/refactor-specialistgit clone --depth 1 https://github.com/eco-ansible-content/agentic-workflowsWrote 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/eco-ansible-content/agentic-workflows/refactor-specialist)<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/refactor-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/refactor-specialist.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 | $0.00015 | $0.00434 |
| Opus 5 | $0.00008 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
refactor-specialist 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 4d 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.
What it actually says
Refactor Specialist
Extract shared code to plugins/module_utils/ every 10 modules.
Trigger
Every 10 completed modules
Process
- Analyze modules for duplicated code
- Extract to
module_utils/<name>.pyor.ps1 - Update modules to import from module_utils
- Run regression tests
- Verify no breaking changes
Success Criteria
- ✅ Duplicated code extracted
- ✅ All tests still pass
- ✅ Modules updated to use utilities
Learned Patterns (from production runs)
This section is automatically maintained by insights-sync-specialist. Patterns captured from real production runs and applied here for future reference.
Pattern: Provider-Auto-Detection
New providers with extra mandatory params MUST be excluded from auto-detection loops; use Where-Object filter on provider list
Source: Team insight from Hen Yaish
Pattern: Required-If-Limitations
Ansible required_if cannot condition on two params; move to manual validation in module body, preserve EXACT original error messages
Source: Team insight from Hen Yaish
Pattern: Failure-Test-Regression
When modifying module validation, always run FAILURE tests (not just success); existing tests assert on exact error message strings
Source: Team insight from Hen Yaish
Pattern: Provider-Isolation
Providers requiring explicit opt-in (extra params) must not participate in auto-detection; mirror the msix conditional exclusion pattern
Source: Team insight from Hen Yaish
Pattern: PowerShell-Error-Handling
Never use $Error.Clear(), prefer try/catch over ErrorAction, use SilentlyContinue not Ignore, don't set $ErrorActionPreference globally
Source: Team insight from Hen Yaish
Pattern: PowerShell-Import-Conventions
Use #AnsibleRequires not #Requires, import Ansible.Basic not Ansible.ModuleUtils.Legacy, no -Module flag, standardize imports
Source: Team insight from Hen Yaish
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.
- 4d ago First seen · 63 lines · 15 tokens per session scan A 526986cbf68c
refactor-specialist is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 11d ago), licensed MIT. It adds 15 tokens to every session and 434 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.