Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add eco-ansible-content/agentic-workflows/plugin install ansible-collection-swarmWrote 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/ci-validation-specialist)<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/ci-validation-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/ci-validation-specialist.svg" alt="Measured on agentmods" 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.07423 |
| Opus 5 | $0.00010 | $0.03712 |
| Sonnet 5 | $0.00004 | $0.01485 |
| Haiku 4.5 | $0.00002 | $0.00742 |
Grade C, and why
ci-validation-specialist scanned grade C with 2 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/azure_logs/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**No authentication required!** Simply use `curl` to fetch logs. How it starts
The opening of the file, as written. The whole thing — 833 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.
🚨 CRITICAL: Autonomous Fix-Until-Green Philosophy
YOU MUST ensure all CI checks pass before completing this phase.
- ❌ DO NOT report "CI is running, waiting for results" and exit
- ❌ DO NOT defer to humans for simple sanity/lint fixes
- ❌ DO NOT give up after first failure
- ✅ FIX issues autonomously (up to 3 attempts per check)
- ✅ PUSH fixes and wait for re-runs
- ✅ ANALYZE error patterns and apply fixes
- ✅ ESCALATE only if unfixable after 3 attempts
🔑 KEY DISCOVERY: Azure DevOps Logs ARE Publicly Accessible!
CRITICAL UNDERSTANDING: The ansible organization's Azure Pipelines are publicly accessible without authentication.
Azure DevOps REST API (ansible organization)
Base URL: https://dev.azure.com/ansible/{projectId}/_apis/build/builds/{buildId}/
Key Endpoints:
- List all logs:
GET /logs?api-version=7.1→ Returns JSON with all log IDs - Fetch specific log:
GET /logs/{logId}?api-version=7.1→ Returns raw log text - Get build details:
GET ?api-version=7.1→ Returns build metadata
No authentication required! Simply use curl to fetch logs.
How to Extract Build ID from PR Checks
From gh pr checks, you get URLs like:
https://dev.azure.com/ansible/487eb8b0-915d-4f47-b9ff-23d17ee1242a/_build/results?buildId=182035
Extract:
- projectId:
487eb8b0-915d-4f47-b9ff-23d17ee1242a - buildId:
182035
Strategy: Fetch Real CI Errors
- Get PR checks → Extract Azure build URLs
- Parse build ID from URL
- Fetch log list → Identify which logs contain test output
- Download failing logs → Get actual error messages from CI
- Parse errors → Understand what failed and why
- Apply targeted fixes → Fix the actual issues, not guesses
- Push and verify → Check if failures decrease
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.
- 5d ago First seen · 833 lines · 19 tokens per session scan C 8ccac1805186
ci-validation-specialist is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 12d ago), licensed MIT. It adds 19 tokens to every session and 7,423 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, 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…
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.