learning-evolution-specialist

learning-evolution-specialist is an agent for Claude Code from eco-ansible-content/agentic-workflows. It costs 24 tokens per session (5,585 once invoked), scanned A, original, MIT.

A continuous-improvement role for a Windows Ansible collection swarm, where several agents build automation modules. It studies failures and successes to update agent instructions and documentation.

In plain words
What is it for?
Use it after major failures, CI failures, successful workflows, or periodic reviews to analyze logs and improve the swarm.
Why use it?
It turns repeated problems and useful patterns into guidance for later work instead of leaving each failure isolated.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; names the AskUserQuestion tool.

Part of the agentic-workflows plugin — 2 skills, 22 agents, 1 plugin shipped together

Good fit Use it after major failures, CI failures, successful workflows, or periodic reviews to analyze logs and improve the swarm.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-learning-evolution-specialist
Install

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.

Clone the repo
git clone --depth 1 https://github.com/eco-ansible-content/agentic-workflows

Made for: Claude Code.

Or install agentic-workflows, the plugin that ships this one along with the rest of its 2 skills, 22 agents, 1 plugin.

Wrote 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.

agentmods badge for learning-evolution-specialist

README.md
[![agentmods](https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-learning-evolution-specialist/github.svg)](https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-learning-evolution-specialist)
Your own site
<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.

agentmods 80×15 button for learning-evolution-specialist

Your own site · 80×15
<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>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,585 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash d10c5d0598dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

claude/agents/windows-collection-swarm-learning-evolution-specialist.md · 787 lines

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:

  1. After Major Failures: When any agent exhausts 3 attempts and escalates
  2. After CI/CD Failures: When CI Validation Specialist reports unfixable issues
  3. After Successful Completion: At end of workflow to capture best practices
  4. On-Demand: When Lead Architect requests learning review
  5. 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

  1. Analyze all agent logs and execution history
  2. Read any file in the swarm workspace
  3. Ask targeted questions to users for clarification
  4. Update agent definitions to incorporate learnings
  5. Update guides and documentation based on new knowledge
  6. Create new examples for common patterns
  7. Maintain lessons learned database (docs/lessons_learned.md)
  8. 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>"
}

Read the full file on GitHub · 787 lines

Changes

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.

  1. 10d ago First seen · 787 lines · 24 tokens per session scan A d10c5d0598dc

Subscribe to this mod's changes

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.