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 abdullahkhawer/devops-skills --skill ansible-cligit clone --depth 1 https://github.com/abdullahkhawer/devops-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/abdullahkhawer/devops-skills/ansible-cli)<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/ansible-cli"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/ansible-cli/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/abdullahkhawer/devops-skills/ansible-cli"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/ansible-cli.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.00033 | $0.01013 |
| Opus 5.5 | $0.00013 | $0.00405 |
| Sonnet 5.5 | $0.00007 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
ansible-cli 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 23d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible CLI Skill
Use the inventory table and rules below when constructing all ansible/ansible-playbook commands.
Configuration
Update the table below with your inventory file paths before using this skill:
| Environment | Inventory File | Vault Password File |
|---|---|---|
| Production | <your-prod-inventory> |
<your-prod-vault-pass-file> |
| Staging / Non-Prod | <your-nonprod-inventory> |
<your-nonprod-vault-pass-file> |
If the target environment is unclear, ask the user before running any command.
Prerequisites (one-time setup by user)
If ansible is not installed or no inventory is configured, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself.
brew install ansible
ansible-inventory -i <inventory-file> --list
Command Format
Always pass -i <inventory-file> explicitly — never rely on a default inventory:
ansible-playbook -i <inventory-file> <playbook.yml> [options]
Examples
# Dry run against non-prod
ansible-playbook -i <your-nonprod-inventory> <playbook.yml> --check --diff
# List hosts targeted by a play
ansible-playbook -i <your-nonprod-inventory> <playbook.yml> --list-hosts
Available Commands
Read-only (safe, no confirmation needed)
| Command | Description |
|---|---|
ansible-inventory -i <inv> --list/--graph |
Show inventory structure |
ansible <group> -i <inv> -m ping |
Check host connectivity (no state change) |
ansible <group> -i <inv> -m setup |
Gather facts about hosts |
ansible-playbook -i <inv> <playbook> --check --diff |
Dry-run a playbook, showing what would change |
ansible-playbook -i <inv> <playbook> --list-hosts |
List hosts a playbook would target |
ansible-playbook -i <inv> <playbook> --list-tasks |
List tasks a playbook would run |
ansible-lint <playbook> |
Lint a playbook for issues |
ansible-doc <module> |
Show documentation for a module |
ansible-vault view <file> |
View encrypted vault contents (still a credential — handle per Rules) |
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.
- 23d ago First seen · 90 lines · 33 tokens per session scan A 275f36ff3878
ansible-cli is a skill published in the GitHub repository abdullahkhawer/devops-skills (8 stars, last pushed 24d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,013 once invoked, about $0.0001 per session on Opus 5.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-09-23.
Other skills, from other repositories
lore
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user…
docs-manage
Manage the Grounded Docs MCP Server documentation index. Covers scraping and indexing documentation from URLs or local files, refreshing existing indexes with changed content, removing libraries from the index, and compacting the SQLite store. Use when you need to add, update, or delete indexed documentation, or…
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
backseat-driver-testing
Testing strategies for Calva Backseat Driver MCP tools. Use when: Testing Backseat Driver, validating tool updates, testing structural editing workflows, verifying REPL evaluation with who-tracking, testing shadow-cljs runtime discovery and targeting, testing output log filtering, testing load-file tool, smoke testing…
editing-clojure-files
Structural editing of Clojure files using Backseat Driver tools. Use when editing or planning edits: creating/adding/inserting/replacing/deleting top-level forms, fixing bracket balance, resolving indentation issues, planning multi-edit sequences, recovering from failed edits, or working with Rich Comment Forms in…