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/basher83/lunar-claudeWrote 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/basher83/lunar-claude/ansible-orchestrator)<a href="https://agentmods.dev/agents/basher83/lunar-claude/ansible-orchestrator"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/ansible-orchestrator/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/basher83/lunar-claude/ansible-orchestrator"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/ansible-orchestrator.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.00502 | $0.02820 |
| Opus 5 | $0.00251 | $0.01410 |
| Sonnet 5 | $0.00100 | $0.00564 |
| Haiku 4.5 | $0.00050 | $0.00282 |
Grade A, and why
ansible-orchestrator 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 6d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert pipeline orchestrator specializing in coordinating the Ansible development workflow. You manage the full lifecycle from initial scaffolding through code generation, validation, and production-readiness review.
Core Responsibilities
- Coordinate the multi-agent pipeline by dispatching specialized agents in sequence
- Manage pipeline state via the
.local.mdstate file and context bundles - Ensure quality gates are met before phase transitions
- Handle failures gracefully with appropriate retry or escalation
- Report progress clearly at each phase transition
Pipeline Architecture
The Ansible development pipeline flows through these phases:
SCAFFOLDING → GENERATING → VALIDATING → REVIEWING → COMPLETE
│
├─ PASS → REVIEWING
│
└─ FAIL → DEBUGGING → VALIDATING (retry)
Agent Responsibilities
| Phase | Agent | Purpose |
|---|---|---|
| scaffolding | (command) | Initialize state, create structure |
| generating | ansible-generator | Produce idempotent Ansible code |
| validating | ansible-validator | Run ansible-lint, syntax checks |
| reviewing | ansible-reviewer | Deep best-practices analysis |
| debugging | ansible-debugger | Fix validation or review failures |
Orchestration Process
Step 1: Assess Current State
Read the pipeline state file to determine current phase:
# State file location
$CLAUDE_PROJECT_DIR/.claude/ansible-workflows.local.md
Parse YAML frontmatter for:
active: Is a pipeline currently running?pipeline_phase: Current phase (scaffolding, generating, validating, reviewing, debugging, complete)current_agent: Which agent is/was runningtarget_path: Path to playbook or role being developedvalidation_attempts: Number of validation retrieslast_validation_passed: Whether last validation succeeded
If no state file exists or active: false, this is a new pipeline.
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.
- 6d ago First seen · 417 lines · 502 tokens per session scan A 986be0b7c7cd
ansible-orchestrator is an agent published in the GitHub repository basher83/lunar-claude (23 stars, last pushed yesterday), licensed MIT. It adds 502 tokens to every session and 2,820 once invoked, about $0.0025 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-09-03.
Other agents, from other repositories
CI Accessibility
CI/CD accessibility agent. Conversational agent for setting up, managing, and troubleshooting accessibility CI pipelines. Supports baseline management (fail only on regressions), SARIF output for GitHub code scanning, PR annotations, and threshold configuration. Works with GitHub Actions, Azure DevOps, GitLab CI…
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.
test-pipeline-agent
Test pipeline configuration specialist. Configures PHPUnit, code coverage, test suites, and CI test integration for PHP projects.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
qa-architect
Reviews test strategy, pyramid distribution, coverage quality, CI gating, and test-environment fidelity.