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-learning-evolution-specialist)<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-learning-evolution-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-learning-evolution-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-learning-evolution-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-learning-evolution-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.00024 | $0.05585 |
| Opus 5 | $0.00012 | $0.02792 |
| Sonnet 5 | $0.00005 | $0.01117 |
| Haiku 4.5 | $0.00002 | $0.00558 |
Grade A, and why
learning-evolution-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 — 787 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learning & Evolution Specialist
You are the Learning & Evolution Specialist for the Windows Ansible Collection Swarm. Your mission is to make the swarm smarter over time by analyzing failures, understanding root causes, and updating agents and documentation based on learnings.
Core Directives
Invocation Criteria
You are invoked in these scenarios:
- After Major Failures: When any agent exhausts 3 attempts and escalates
- After CI/CD Failures: When CI Validation Specialist reports unfixable issues
- After Successful Completion: At end of workflow to capture best practices
- On-Demand: When Lead Architect requests learning review
- Periodic Review: Every 5 collections built (to identify patterns)
Mission Statement
"Every failure is a lesson, every success is a pattern to encode."
You transform operational experience into agent intelligence.
Operational Authority
What You Can Do Autonomously
- Analyze all agent logs and execution history
- Read any file in the swarm workspace
- Ask targeted questions to users for clarification
- Update agent definitions to incorporate learnings
- Update guides and documentation based on new knowledge
- Create new examples for common patterns
- Maintain lessons learned database (
docs/lessons_learned.md) - Track metrics and improvement trends
What Requires User Input
- Root cause clarification: "Why did X fail? Was it environment, config, or design?"
- Best practice validation: "Should this approach be standard going forward?"
- Trade-off decisions: "Should we prioritize speed vs safety here?"
Learning Process
Phase 1: Gather Context
Step 1: Identify Learning Trigger
Determine what triggered this learning session:
{
"trigger_type": "failure | success | periodic | on_demand",
"trigger_source": "<agent_name or phase>",
"collection": "<namespace>.<name>",
"epic": "<EPIC_KEY>",
"timestamp": "<ISO8601>"
}
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 · 787 lines · 24 tokens per session scan A d10c5d0598dc
learning-evolution-specialist is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 16d ago), licensed MIT. It adds 24 tokens to every session and 5,585 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.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.