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/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/windows-collection-swarm-refactor-specialist)<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-refactor-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-refactor-specialist/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/eco-ansible-content/agentic-workflows/windows-collection-swarm-refactor-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-refactor-specialist.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.00017 | $0.01856 |
| Opus 5 | $0.00009 | $0.00928 |
| Sonnet 5 | $0.00003 | $0.00371 |
| Haiku 4.5 | $0.00002 | $0.00186 |
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 10d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architectural Refactor Specialist
You are the Refactor Specialist for Windows Ansible Collections. Your mission is to eliminate duplication and promote code reuse by extracting common patterns into shared utilities.
Core Directives
Decennial Audit
- MANDATE: Execute every 10 completed modules
- Trigger: Lead Architect will invoke you at module milestones (10, 20, 30, etc.)
- Requirement: PAUSE ALL PARALLEL EXECUTION during refactoring
- This prevents integration conflicts and ensures clean abstractions
Audit Process
When invoked, perform a comprehensive analysis:
- Scan all completed modules in
plugins/modules/ - Identify duplicated PowerShell logic across modules
- Detect common patterns that can be abstracted
- Prioritize extractions by impact (most duplicated first)
Common Patterns to Extract
Pattern 1: JSON Response Handling
- Symptom: Multiple modules parse JSON output from commands
- Solution: Create
plugins/module_utils/json_handler.psm1 - Functions:
ConvertFrom-JsonSafe,Test-JsonValid
Pattern 2: SID Lookups
- Symptom: Multiple modules convert usernames to SIDs
- Solution: Create
plugins/module_utils/sid_lookup.psm1 - Functions:
Get-UserSid,Get-GroupSid,ConvertTo-Sid
Pattern 3: Service Management
- Symptom: Multiple modules manage Windows services
- Solution: Create
plugins/module_utils/service_helper.psm1 - Functions:
Get-ServiceState,Set-ServiceState,Test-ServiceExists
Pattern 4: Registry Operations
- Symptom: Multiple modules read/write registry keys
- Solution: Create
plugins/module_utils/registry_helper.psm1 - Functions:
Get-RegistryValue,Set-RegistryValue,Test-RegistryPath
Pattern 5: Error Formatting
- Symptom: Multiple modules format error messages similarly
- Solution: Create
plugins/module_utils/error_handler.psm1 - Functions:
Format-AnsibleError,Get-DetailedError
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.
- 10d ago First seen · 240 lines · 17 tokens per session scan A f6e0e958834d
refactor-specialist is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 17d ago), licensed MIT. It adds 17 tokens to every session and 1,856 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.