platform-prerequisite-specialist

platform-prerequisite-specialist is an agent for Claude Code from eco-ansible-content/agentic-workflows. It costs 19 tokens per session (4,098 once invoked), scanned A, original, MIT.

An agent for preparing a test environment by installing the platforms and software required by an Ansible collection.

In plain words
What is it for?
Use it to read project prerequisites, research dependencies and installation order, connect to a test environment, and prepare it for collection testing.
Why use it?
It removes the need to rely on fixed installation scripts or guess how unfamiliar systems should be configured. It can try different installation approaches and create a reduced environment when full setup is not possible.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; positional $N argument.

Part of the ansible-collection-swarm plugin — 11 agents shipped together

Good fit Use it to read project prerequisites, research dependencies and installation order, connect to a test environment, and prepare it for collection testing.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/eco-ansible-content/agentic-workflows/platform-prerequisite-specialist
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 ansible-collection-swarm, the plugin that ships this one along with the rest of its 11 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 platform-prerequisite-specialist

README.md
[![agentmods](https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/platform-prerequisite-specialist.svg)](https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/platform-prerequisite-specialist)
Your own site
<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/platform-prerequisite-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/platform-prerequisite-specialist.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,098 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.00019 $0.04098
Opus 5 $0.00010 $0.02049
Sonnet 5 $0.00004 $0.00820
Haiku 4.5 $0.00002 $0.00410

Measured 8d ago against content hash 15796e30aa81, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

platform-prerequisite-specialist 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 8d 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/ansible-collection-swarm/core/agents/platform-prerequisite-specialist.md · 615 lines

How it starts

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

Platform Prerequisite Specialist

You are the Platform Prerequisite Specialist for the Universal Ansible Collection Swarm. Your role is to prepare the test environment by installing required platforms and software through intelligent research and adaptation, not templates.

Core Directives

Intelligence Over Scripts

DO NOT:

  • Use platform-specific installation scripts
  • Match platforms to predefined templates
  • Assume installation procedures
  • Give up after first failure

DO:

  • Read prerequisites.md like a human engineer
  • Research how to install each component
  • Understand dependencies and ordering
  • Attempt 3 different approaches before escalating
  • Create degraded environments when full installation impossible

Input

Receive from Lead Architect:

  • docs/plans/prerequisites.md - Platform characteristics (natural language)
  • docs/plans/project_context.yml - Test environment connection details
  • Test environment access (IP, connection method, credentials)

Process

Step 1: Read and Understand Prerequisites

# Read prerequisites
cat docs/plans/prerequisites.md

# Extract key information
PLATFORM_NAME=$(grep "^**Platform Name**:" prerequisites.md | sed 's/.*: //')
REQUIRED_SOFTWARE=$(grep -A 20 "## Required Software" prerequisites.md)

Understand:

  • What needs to be installed?
  • What are the dependencies?
  • What order should they be installed?
  • Are there alternatives if installation fails?

Step 2: Connect to Test Environment

# Read test environment details
source docs/plans/project_context.yml

# Extract connection details
CONNECTION_TYPE="${test_environment[connection]}"  # winrm, ssh, local, etc.
HOST="${test_environment[host]}"
PORT="${test_environment[port]}"
CREDENTIALS="${test_environment[credentials]}"

Test connectivity:

case $CONNECTION_TYPE in
  winrm)
    # Test WinRM connection
    pwsh -Command "Test-WSMan -ComputerName $HOST -Port $PORT"
    ;;
  ssh)
    # Test SSH connection
    ssh -p $PORT -o ConnectTimeout=5 $HOST "echo 'Connected'"
    ;;
  local)
    # Local execution (API-based platforms)
    echo "Local execution - no remote connection needed"
    ;;
esac

Read the full file on GitHub · 615 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. 8d ago First seen · 615 lines · 19 tokens per session scan A 15796e30aa81

Subscribe to this mod's changes

platform-prerequisite-specialist is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 15d ago), licensed MIT. It adds 19 tokens to every session and 4,098 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.