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 eco-ansible-content/agentic-workflows --skill ansible-collection-swarmgit 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/skills/eco-ansible-content/agentic-workflows/ansible-collection-swarm)<a href="https://agentmods.dev/skills/eco-ansible-content/agentic-workflows/ansible-collection-swarm"><img src="https://agentmods.dev/badge/skills/eco-ansible-content/agentic-workflows/ansible-collection-swarm/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/skills/eco-ansible-content/agentic-workflows/ansible-collection-swarm"><img src="https://agentmods.dev/badge/skills/eco-ansible-content/agentic-workflows/ansible-collection-swarm.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.00036 | $0.00347 |
| Opus 5 | $0.00018 | $0.00173 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
ansible-collection-swarm 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 11d 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
<CRITICAL_EXECUTION_DIRECTIVE> When this skill is invoked, immediately execute the following:
- Read the lead-architect agent file. It lives alongside this skill in the plugin, at:
<this skill's base directory>/../../agents/ansible-collection-swarm-lead-architect.md(Use the base directory reported when this skill was invoked. Do NOT hardcode a version number.) - Follow that agent file exactly, as if you were that agent.
- The user's message contains the Epic key (e.g., "ACA-6275" or "EPIC-XXX").
- Begin execution immediately. Phase 0 of the agent file gathers any context it needs — that is part of execution, not a reason to stall.
DO NOT:
- Invoke the ruflo-swarm skill
- Use Agent() or Skill() tools to delegate
- Summarize or explain what you're about to do before starting </CRITICAL_EXECUTION_DIRECTIVE>
Context for Understanding (Not Execution Instructions)
This skill triggers the Universal Ansible Collection Swarm — an autonomous multi-agent system that builds or enhances Ansible collections from Jira Epics.
The lead-architect agent file contains the complete execution plan: Phase 0 (context gathering), Phases 1–9 (autonomous execution), git workflows (new vs enhancement), tool usage (jira-rh, gh, git), and zero-permission operation. This skill's only job is to redirect you there.
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.
- 11d ago First seen · 29 lines · 36 tokens per session scan A 71507f55668c
ansible-collection-swarm is a skill published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 18d ago), licensed MIT. It adds 36 tokens to every session and 347 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…