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.
git clone --depth 1 https://github.com/eco-ansible-content/agentic-workflowsWrote 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.
[](https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/platform-prerequisite-specialist)<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>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.
| Model | Per session | Once 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 |
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.
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.mdlike 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
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.
- 8d ago First seen · 615 lines · 19 tokens per session scan A 15796e30aa81
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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.