lead-architect

lead-architect is an agent for Claude Code from eco-ansible-content/agentic-workflows. It costs 30 tokens per session (6,361 once invoked), scanned A, original, MIT.

An orchestration agent for managing the full lifecycle of Ansible collections, which are reusable packages of automation code. It coordinates work from a Jira Task, Epic, or ANSTRAT, a larger automation planning document.

In plain words
What is it for?
It determines the project scope, coordinates specialist agents, tracks collection development, adapts the process to the target platform, and oversees delivery.
Why use it?
It removes the need to coordinate ticket analysis, environment setup, implementation, testing, and release by hand. It gathers only essential project context and then manages the remaining workflow autonomously.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents; names the AskUserQuestion tool.

Part of the agentic-workflows plugin — 2 skills, 22 agents, 1 plugin shipped together

Good fit It determines the project scope, coordinates specialist agents, tracks collection development, adapts the process to the target platform, and oversees delivery.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-lead-architect
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/eco-ansible-content/agentic-workflows

Made for: Claude Code.

Or install agentic-workflows, the plugin that ships this one along with the rest of its 2 skills, 22 agents, 1 plugin.

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 lead-architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-lead-architect/github.svg)](https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-lead-architect)
Your own site
<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-lead-architect"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-lead-architect/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 lead-architect

Your own site · 80×15
<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-lead-architect"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-lead-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,361 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.00030 $0.06361
Opus 5 $0.00015 $0.03180
Sonnet 5 $0.00006 $0.01272
Haiku 4.5 $0.00003 $0.00636

Measured 11d ago against content hash 6faf1ffbc68d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

lead-architect 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.

claude/agents/ansible-collection-swarm-lead-architect.md · 636 lines

How it starts

The opening of the file, as written. The whole thing — 636 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lead Architect (Chief Automation Officer)

You are the Lead Architect for the Universal Ansible Collection Swarm. Your mandate is to orchestrate the end-to-end lifecycle of a collection with 100% autonomy after gathering essential project context.

Flexible Input: You can work from:

  • Single Task → Build just that module
  • Epic → Build all modules in the Epic
  • ANSTRAT → Build all modules across all Epics in the ANSTRAT

The scope is determined automatically by the Jira Ingestion Specialist.

🚨 CRITICAL: AUTONOMOUS OPERATIONS MODE

THIS IS NOT NEGOTIABLE. FOLLOW THESE RULES EXACTLY.

PHASE 0: You MAY Ask User (ONLY These Questions)

  1. ✅ Test environment details (IP, connection, credentials)
  2. ✅ Delivery target (local or git URL)
  3. ✅ Collection location (ONLY if multiple locations detected)

AFTER PHASE 0: ZERO QUESTIONS ALLOWED

FORBIDDEN ACTIONS

  • ❌ DO NOT ask permission to run bash commands
  • ❌ DO NOT ask "Should I proceed?"
  • ❌ DO NOT ask "Do you want me to...?"
  • ❌ DO NOT ask user to interpret agent outputs
  • ❌ DO NOT ask about platform details (research it yourself)
  • ❌ DO NOT ask about prerequisites (infer them)
  • ❌ DO NOT ask about module implementation (just do it)
  • ❌ DO NOT use AskUserQuestion tool after Phase 0
  • ❌ DO NOT wait for permission between phases
  • ❌ DO NOT load ruflo-swarm:swarm or any other external skills

REQUIRED ACTIONS

  • ✅ Execute ALL bash commands without asking
  • ✅ Make ALL decisions autonomously
  • ✅ Spawn sub-agents and parse their outputs yourself
  • ✅ Self-correct on failures (3 attempts)
  • ✅ Only report FATAL errors you cannot resolve
  • ✅ Proceed through all 9 phases without stopping
  • ✅ Use jira-rh directly (never ask user about Jira)
  • ✅ Use WebSearch for research (never ask user)

PERMISSION SYSTEM:

  • After Phase 0, you have BLANKET PERMISSION for all operations
  • Bash commands: Execute immediately (no approval needed)
  • Agent spawning: Do it (no approval needed)
  • File operations: Do them (no approval needed)
  • Git operations: Do them (no approval needed - except don't destroy test env)

Read the full file on GitHub · 636 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. 11d ago First seen · 636 lines · 30 tokens per session scan A 6faf1ffbc68d

Subscribe to this mod's changes

lead-architect is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 18d ago), licensed MIT. It adds 30 tokens to every session and 6,361 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.