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.
npx skills add stoleas/ansible-skills --skill role-developergit clone --depth 1 https://github.com/stoleas/ansible-skillsWrote 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/skills/stoleas/ansible-skills/role-developer)<a href="https://agentmods.dev/skills/stoleas/ansible-skills/role-developer"><img src="https://agentmods.dev/badge/skills/stoleas/ansible-skills/role-developer.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.00109 | $0.05149 |
| Opus 5 | $0.00055 | $0.02575 |
| Sonnet 5 | $0.00022 | $0.01030 |
| Haiku 4.5 | $0.00011 | $0.00515 |
Grade A, and why
role-developer 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 7d 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 — 872 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role Developer Skill
Develop comprehensive Ansible roles following Red Hat Communities of Practice (CoP) standards with complete testing, validation, and documentation.
Core Role Concepts
Roles in the Type-Function Pattern
-
Function Roles: Implement reusable capabilities (e.g.,
apache_install,postgresql_config)- Single, focused purpose
- Reusable across multiple types
- Self-contained with all dependencies documented
-
Component Roles: Smaller roles used within function roles for complex implementations
- Break large functions into maintainable components
- Used via
include_roleorimport_rolewithin parent role
Role Naming Standards
CRITICAL: No dashes in role names - they cause collection packaging issues.
Good naming:
apache_install
postgresql_config
firewall_setup
monitoring_agent
Bad naming:
apache-install # Dashes not allowed
postgresqlConfig # CamelCase not allowed
fw_setup # Abbreviations discouraged
monitoring-agent # Dashes not allowed
Naming convention:
- Snake_case exclusively
- No dashes (breaks collections)
- No abbreviations (clarity over brevity)
- Verb_noun pattern when appropriate (
install_apache,configure_firewall) - Descriptive names that indicate purpose
Complete Role Structure
Every role must include these components:
role_name/
├── defaults/
│ └── main.yml # User-facing default variables
├── files/ # Static files
├── handlers/
│ └── main.yml # Event handlers (service restarts, etc.)
├── meta/
│ ├── main.yml # Role metadata and dependencies
│ └── argument_specs.yml # Argument validation (Ansible 2.11+)
├── molecule/ # Testing with Molecule
│ └── default/
│ ├── molecule.yml # Molecule configuration
│ ├── converge.yml # Test playbook
│ └── verify.yml # Verification tests
├── tasks/
│ └── main.yml # Main task list (orchestrates includes)
├── templates/ # Jinja2 templates
├── tests/
│ ├── inventory # Test inventory
│ └── test.yml # Legacy test playbook
├── vars/
│ ├── main.yml # Internal role variables
│ ├── RedHat.yml # RedHat-specific variables
│ └── Debian.yml # Debian-specific variables
├── README.md # Comprehensive documentation
└── .ansible-lint # ansible-lint configuration
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/argument-specs-reference.md 12 KB
- references/idempotency-guide.md 14 KB
- references/variable-naming.md 9.2 KB
- templates/.ansible-lint 968 B
- templates/molecule-scenario/molecule/default/converge.yml 201 B
- templates/molecule-scenario/molecule/default/molecule.yml 1.4 KB
- templates/molecule-scenario/molecule/default/verify.yml 1.5 KB
- templates/role-skeleton/defaults/main.yml 1.4 KB
- templates/role-skeleton/handlers/main.yml 401 B
- templates/role-skeleton/meta/argument_specs.yml 1.6 KB
- templates/role-skeleton/meta/main.yml 574 B
- templates/role-skeleton/README.md 2.7 KB
- templates/role-skeleton/tasks/main.yml 1.3 KB
- templates/role-skeleton/tests/inventory 35 B
- templates/role-skeleton/tests/test.yml 220 B
- templates/role-skeleton/vars/Debian.yml 667 B
- templates/role-skeleton/vars/main.yml 460 B
- templates/role-skeleton/vars/RedHat.yml 667 B
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.
- 7d ago First seen · 872 lines · 109 tokens per session scan A 088ffafd4478
role-developer is a skill published in the GitHub repository stoleas/ansible-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 109 tokens to every session and 5,149 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…