ansible-orchestrator

ansible-orchestrator is an agent for Claude Code from basher83/lunar-claude. It costs 502 tokens per session (2,820 once invoked), scanned A, original, MIT.

An agent that coordinates the full lifecycle of Ansible automation, from initial structure through code generation, validation, review, and debugging. It moves work between specialized agents and tracks the current phase.

In plain words
What is it for?
Use it to run an end-to-end process for creating production-ready Ansible playbooks or roles, including linting, validation, review, and fixes.
Why use it?
It prevents the workflow from stopping after code generation or validation by enforcing quality gates and retrying failed work through debugging.

Agent for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable. Also seen: model in frontmatter.

Part of the ansible-workflows plugin — 8 skills, 3 commands, 5 agents shipped together

Good fit Use it to run an end-to-end process for creating production-ready Ansible playbooks or roles, including linting, validation, review, and fixes.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/basher83/lunar-claude/ansible-orchestrator
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/basher83/lunar-claude

Made for: Claude Code.

Or install ansible-workflows, the plugin that ships this one along with the rest of its 8 skills, 3 commands, 5 agents.

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 ansible-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/basher83/lunar-claude/ansible-orchestrator/github.svg)](https://agentmods.dev/agents/basher83/lunar-claude/ansible-orchestrator)
Your own site
<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.

agentmods 80×15 button for ansible-orchestrator

Your own site · 80×15
<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>
Per session 502 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,820 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.00502 $0.02820
Opus 5.5 $0.00201 $0.01128
Sonnet 5.5 $0.00100 $0.00564
Haiku 4.5 $0.00050 $0.00282

Measured 2mo ago against content hash 986be0b7c7cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

plugins/infrastructure/ansible-workflows/agents/ansible-orchestrator.md · 417 lines

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

  1. Coordinate the multi-agent pipeline by dispatching specialized agents in sequence
  2. Manage pipeline state via the .local.md state file and context bundles
  3. Ensure quality gates are met before phase transitions
  4. Handle failures gracefully with appropriate retry or escalation
  5. 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 running
  • target_path: Path to playbook or role being developed
  • validation_attempts: Number of validation retries
  • last_validation_passed: Whether last validation succeeded

If no state file exists or active: false, this is a new pipeline.

Read the full file on GitHub · 417 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. 2mo ago First seen · 417 lines · 502 tokens per session scan A 986be0b7c7cd

Subscribe to this mod's changes

ansible-orchestrator is an agent published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 502 tokens to every session and 2,820 once invoked, about $0.0020 per session on Opus 5.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.

Related

ansible-orchestrator compared with agents from other repositories

ansible-orchestrator next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ansible-orchestratorbasher83/lunar-claudeAgent23todayMITA502Claude Code
jenkins-expert0xfurai/claude-code-subagentsAgent1.0k2d agoMITA31Claude Code
monorepo-managerJosephHampton/awesome-gemini-cli-subagentsAgent992d agoCC0-1.0A0Claude Code
gatetonone-ai/tononeAgent77todayMITA19Claude Code
meeting-organizerjuliusz-cwiakalski/agentic-delivery-osAgent43todayMITA9Claude Code
platform-engineerulises-jeremias/agent-toolkitAgent19todayMITA88Claude Code
analystrjmurillo/ai-agentsAgent49todayMITA0Claude Code