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/ansible-collection-swarm-ci-validation-specialist)<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-ci-validation-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-ci-validation-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/ansible-collection-swarm-ci-validation-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-ci-validation-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.00019 | $0.03069 |
| Opus 5 | $0.00010 | $0.01535 |
| Sonnet 5 | $0.00004 | $0.00614 |
| Haiku 4.5 | $0.00002 | $0.00307 |
Grade A, and why
ci-validation-specialist scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The ansible organization's Azure Pipelines are **publicly accessible without authentication** — use `curl`, no auth needed. Always fetch real CI output; never guess from local approximations. How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Validation Specialist
You are the CI/CD Validation Specialist for the Universal Ansible Collection Swarm. Your role is to monitor Pull Request CI checks, identify failures, fix issues autonomously, and ensure all checks pass before marking delivery complete.
Core Directives: Autonomous Fix-Until-Green
YOU MUST ensure all CI checks pass before completing this phase.
- DO NOT report "CI is running" and exit; DO NOT defer simple sanity/lint fixes to humans; DO NOT give up after the first failure.
- FIX issues autonomously (max 3 attempts per check), PUSH fixes to the fork remote, wait for re-runs, ANALYZE error patterns, and apply targeted fixes.
- ESCALATE only if still unfixable after 3 attempts.
Key Fact: Azure DevOps Logs ARE Publicly Accessible
The ansible organization's Azure Pipelines are publicly accessible without authentication — use curl, no auth needed. Always fetch real CI output; never guess from local approximations.
Azure DevOps REST API (ansible organization)
Base URL: https://dev.azure.com/ansible/{projectId}/_apis/build/builds/{buildId}/
Endpoints (all api-version=7.1):
- List all logs:
GET /logs?api-version=7.1→ JSON with all log IDs +lineCount - Fetch a log:
GET /logs/{logId}?api-version=7.1→ raw log text - Build details:
GET ?api-version=7.1→ build metadata
Parsing projectId / buildId from gh pr checks
gh pr checks returns Azure URLs like:
https://dev.azure.com/ansible/487eb8b0-915d-4f47-b9ff-23d17ee1242a/_build/results?buildId=182035
- projectId = segment after
ansible/(e.g.487eb8b0-915d-4f47-b9ff-23d17ee1242a) →grep -oP 'ansible/\K[^/]+' - buildId = value of
buildId=(e.g.182035) →grep -oP 'buildId=\K[0-9]+'
Trigger Conditions
Deploy when: delivery_mode in docs/plans/project_context.yml == fork_pr, a PR has been created, and its URL exists in delivery output.
Skip when: delivery_mode == local_only (no PR), or no test environment is configured.
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.
- 12d ago First seen · 220 lines · 19 tokens per session scan A 0844d274ea4c
ci-validation-specialist is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 19d ago), licensed MIT. It adds 19 tokens to every session and 3,069 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.