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 vinnie357/claude-skills --skill ansible-testinggit clone --depth 1 https://github.com/vinnie357/claude-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/vinnie357/claude-skills/ansible-testing)<a href="https://agentmods.dev/skills/vinnie357/claude-skills/ansible-testing"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/ansible-testing/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/vinnie357/claude-skills/ansible-testing"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/ansible-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.02999 |
| Opus 5 | $0.00026 | $0.01499 |
| Sonnet 5 | $0.00010 | $0.00600 |
| Haiku 4.5 | $0.00005 | $0.00300 |
Grade A, and why
ansible-testing 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
cmd = host.run("curl -s -o /dev/null -w '%{http_code}' http://localhost") How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Testing with Molecule
Activate when setting up Molecule for a role, writing test scenarios, configuring drivers, writing Testinfra assertions, or integrating Ansible tests into CI.
Why Test Ansible Code
Without automated tests:
- Refactoring breaks things silently
- Idempotency regressions go undetected (tasks that should be no-ops make changes on repeated runs)
- Roles stop working on newer OS versions without anyone noticing
Molecule provides a framework to spin up a test environment, run your role against it, verify the end state, and tear it down — all automatically.
Molecule Test Phases
Molecule runs these phases in order when you execute molecule test. molecule test --help states the same list (Test (dependency, cleanup, destroy, syntax, create, prepare, converge, idempotence, side_effect, verify, cleanup, destroy)), but help text is a claim about behavior, not the behavior itself (this exact gap shipped a broken bd diff example in claude-skills-219) — the phase order below is instead cited to molecule 26.6.0's installed molecule/constants.py, whose DEFAULT["scenario"]["test_sequence"] list matches token-for-token. There is no standalone lint phase or molecule lint command in current Molecule — ansible-lint/yamllint are no longer a first-class Molecule action; run them directly (see "Linting" below) or wire them into CI alongside molecule test.
| Phase | What it does |
|---|---|
dependency |
Install role/collection dependencies (per dependency: config) |
cleanup |
Optional: cleanup tasks before destroy |
destroy |
Remove any leftover test instances |
syntax |
Syntax-check the converge playbook |
create |
Spin up fresh test instances (containers or VMs) |
prepare |
Optional: run a prepare playbook before converge |
converge |
Apply your role to the test instances |
idempotence |
Run converge again — assert zero changes |
side_effect |
Optional: apply changes to test failure/recovery scenarios |
verify |
Run your test assertions against live instances |
cleanup |
Optional: cleanup tasks before destroy |
destroy |
Tear down all test instances |
What ships with it
1 file 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.
- 6d ago First seen · 335 lines · 52 tokens per session scan A 716ef01519aa
ansible-testing is a skill published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 2,999 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.