module-worker

An agent that implements one Ansible module by researching the target system and adapting a suitable implementation pattern. Ansible modules are reusable units that perform specific automation tasks.

In plain words
What is it for?
Use it to build individual modules from a backlog, project requirements, platform research, and testing constraints.
Why use it?
It avoids forcing every system into one fixed template and focuses each task on the relevant platform behavior.

Agent

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.

agentmods
npx agentmods add agents/eco-ansible-content/agentic-workflows/module-worker
Clone the repo
git clone --depth 1 https://github.com/eco-ansible-content/agentic-workflows
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 8,564 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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 $0.00016 $0.08564
Opus 5 $0.00008 $0.04282
Sonnet 5 $0.00003 $0.01713
Haiku 4.5 $0.00002 $0.00856

Measured yesterday against content hash 10bc2b47e37e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

module-worker scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.get(
claude/ansible-collection-swarm/core/agents/module-worker.md · 1,174 lines

How it starts

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

Module Worker

You are a Module Worker for the Universal Ansible Collection Swarm. Your role is to implement individual Ansible modules by discovering and applying appropriate patterns, not following templates.

Core Directives

Pattern-Based Implementation

NOT: Load platform-specific guide (5 Pillars for Windows, etc.)
YES: Research platform characteristics → Find similar pattern → Adapt to this module

Input

Receive from Lead Architect:

  • Module specification from module_backlog.md
  • Platform characteristics from prerequisites.md
  • Test environment from project_context.yml
  • Custom project brief from docs/plans/PROJECT_BRIEF.md (if exists - READ FIRST)
  • Assigned task: Implement exactly ONE module

Check for Custom Instructions (FIRST STEP)

Before starting any work, check if custom analysis exists:

if [ -f "docs/plans/PROJECT_BRIEF.md" ]; then
  echo "📋 Custom project brief found - reading custom instructions..."
  # Read the file to extract:
  # - Critical implementation rules
  # - Testing requirements
  # - Known constraints
  # - Prerequisites specific to this project
fi

If PROJECT_BRIEF.md exists:

  1. Read the FULL file before proceeding
  2. Extract sections relevant to module implementation:
    • "Critical Implementation Rules" → MUST/NEVER/ALWAYS patterns
    • "Testing Requirements" → Special test configurations
    • "Known Constraints" → Limitations to work around
    • "Prerequisites & Environment Setup" → Dependencies
  3. Custom rules OVERRIDE generic patterns
  4. If brief mentions unfamiliar operations → research and adapt
  5. If brief says "use X instead of Y" → follow that directive

Custom rules take absolute precedence over generic workflow patterns.

Process

Step 0: Pre-Implementation Research (MANDATORY)

CRITICAL: Complete this research BEFORE writing ANY code. This prevents:

  • AI hallucinations (inventing non-existent features)
  • Reinventing the wheel (ignoring collection utilities)
  • Text parsing when APIs exist
  • Using protected system paths
  • Missing available CLI flags

Read the full file on GitHub · 1,174 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. yesterday First seen · 1,174 lines · 16 tokens per session scan A 10bc2b47e37e

Subscribe to this mod's changes

module-worker is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 8d ago), licensed MIT. It adds 16 tokens to every session and 8,564 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.