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 ansible-scaffold-collectiongit 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/ansible-scaffold-collection)<a href="https://agentmods.dev/skills/stoleas/ansible-skills/ansible-scaffold-collection"><img src="https://agentmods.dev/badge/skills/stoleas/ansible-skills/ansible-scaffold-collection/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.
<a href="https://agentmods.dev/skills/stoleas/ansible-skills/ansible-scaffold-collection"><img src="https://agentmods.dev/badge/skills/stoleas/ansible-skills/ansible-scaffold-collection.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.03572 |
| Opus 5 | $0.00043 | $0.01786 |
| Sonnet 5 | $0.00017 | $0.00714 |
| Haiku 4.5 | $0.00009 | $0.00357 |
Grade A, and why
ansible-scaffold-collection 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.
How it starts
The opening of the file, as written. The whole thing — 687 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Collection Scaffolding Skill
Scaffold complete Ansible collections following Red Hat Communities of Practice (CoP) standards with proper structure, documentation, and testing setup.
What is an Ansible Collection?
An Ansible Collection is a distribution format for Ansible content that can contain:
- Roles - Reusable automation units
- Modules - Custom Ansible modules
- Plugins - Various plugin types (filters, lookups, inventory, etc.)
- Playbooks - Example playbooks and workflows
- Documentation - Comprehensive guides and references
Collections enable:
- Packaging related automation together
- Versioning and distribution via Ansible Galaxy
- Namespace isolation
- Reusable content across organizations
Collection Naming
Format: namespace.collection_name
Rules:
- Namespace: Organization or author identifier (lowercase, underscores allowed)
- Collection name: Descriptive name (lowercase, underscores allowed, no dashes)
- Both must be valid Python identifiers
- Examples:
company.infrastructure,redhat.rhel_system_roles,community.general
Collection Structure
Complete Red Hat CoP compliant collection:
namespace/
└── collection_name/
├── galaxy.yml # Collection metadata (REQUIRED)
├── README.md # Collection documentation (REQUIRED)
├── docs/ # Additional documentation
│ ├── getting_started.md
│ └── guides/
├── meta/
│ └── runtime.yml # Runtime metadata
├── roles/ # Collection roles
│ ├── role_name_1/
│ │ ├── defaults/
│ │ ├── handlers/
│ │ ├── meta/
│ │ │ ├── main.yml
│ │ │ └── argument_specs.yml
│ │ ├── tasks/
│ │ ├── templates/
│ │ ├── vars/
│ │ ├── README.md
│ │ └── molecule/
│ └── role_name_2/
├── plugins/ # Collection plugins
│ ├── modules/ # Custom modules
│ │ └── module_name.py
│ ├── module_utils/ # Shared module utilities
│ ├── filter/ # Jinja2 filters
│ ├── lookup/ # Lookup plugins
│ ├── inventory/ # Inventory plugins
│ ├── callback/ # Callback plugins
│ └── action/ # Action plugins
├── playbooks/ # Example playbooks
│ ├── example_1.yml
│ └── example_2.yml
├── tests/ # Collection-level tests
│ ├── integration/
│ │ └── targets/
│ └── unit/
│ └── plugins/
├── changelogs/ # Changelog management
│ ├── config.yaml
│ └── changelog.yaml
├── .ansible-lint # Linting configuration
├── .yamllint # YAML linting configuration
├── .gitignore
└── LICENSE
What ships with it
4 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.
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.
- 12d ago First seen · 687 lines · 86 tokens per session scan A 3f2c0f94090b
ansible-scaffold-collection is a skill published in the GitHub repository stoleas/ansible-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 3,572 once invoked, about $0.0004 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…