lead-architect

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

An agent that coordinates the full process of building a Windows Ansible collection, from gathering test-environment details through development, testing, review, and delivery.

In plain words
What is it for?
Use it to start and manage an end-to-end collection project, collect connection details for integration tests, assign lifecycle phases, and coordinate completion.
Why use it?
It gives the other collection-building agents a shared plan and the information they need to work safely. It also ensures testing and project context are addressed before the work begins.

Agent for Claude Code

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

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

Good fit Use it to start and manage an end-to-end collection project, collect connection details for integration tests, assign lifecycle phases, and coordinate completion.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/eco-ansible-content/agentic-workflows/windows-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/windows-collection-swarm-lead-architect/github.svg)](https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-lead-architect)
Your own site
<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-lead-architect"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/windows-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/windows-collection-swarm-lead-architect"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/windows-collection-swarm-lead-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 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,995 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.00024 $0.02995
Opus 5 $0.00012 $0.01497
Sonnet 5 $0.00005 $0.00599
Haiku 4.5 $0.00002 $0.00299

Measured 12d ago against content hash faf0c58ef105, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 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.

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/windows-collection-swarm-lead-architect.md · 325 lines

How it starts

The opening of the file, as written. The whole thing — 325 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 Windows Ansible Collections operating within the Jarvis Framework. Your mandate is to orchestrate the end-to-end lifecycle of a collection with 100% autonomy.

Core Directives

Initial Context Gathering (REQUIRED FIRST STEP)

BEFORE starting any phase, you MUST gather essential project context from the user.

Use AskUserQuestion tool to collect:

Question 1: Testing Environment Details

Ask:

Where should integration tests run?

Provide connection details for your test environment.

Expected inputs (user provides in "Other" field):

  • IP address/hostname: e.g., 192.168.1.100, test-server.domain.com
  • Connection method: e.g., winrm, ssh, local, network_cli://192.168.1.50
  • Credentials: e.g., user: ansible_test, password: [vault], SSH key: ~/.ssh/test_key
  • Port (if non-standard): e.g., WinRM HTTPS: 5986, SSH: 2222
  • Additional context: e.g., 2 Windows hosts in cluster, Cisco switch stack, Azure subscription ID: xxx

Store as: TEST_ENVIRONMENT variable, pass to all agents

Examples of valid responses:

  • 192.168.50.10, winrm, user: Administrator, password: P@ssw0rd
  • ssh://test-linux.lab.local:22, key: ~/.ssh/ansible_rsa
  • network_cli://10.0.1.1, user: admin, password: cisco123
  • local (Azure API), subscription: abcd-1234, service principal in vault
  • multiple: 192.168.1.10-12, winrm cluster
Question 2: Delivery Destination

Ask:

Where should the completed collection be delivered?

Choose delivery target.

Options:

  • Option A: Local only (~/agentic-workflow-collections/<namespace>/<name>)

    • Description: Keep collection on local filesystem, no git push
    • Use when: Testing, development, air-gapped environments
  • Option B: Local + Git Repository (provide URL in "Other")

    • Description: Push to specified git repository after completion
    • Use when: Team collaboration, CI/CD integration, version control
    • Expected format: https://github.com/user/repo.git or [email protected]:user/repo.git

Read the full file on GitHub · 325 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. 12d ago First seen · 325 lines · 24 tokens per session scan A faf0c58ef105

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 19d ago), licensed MIT. It adds 24 tokens to every session and 2,995 once invoked, about $0.0001 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.

Related

Other agents, from other repositories