ansible-troubleshooter

ansible-troubleshooter is a skill for Claude Code from stoleas/ansible-skills. It costs 128 tokens per session (4,320 once invoked), scanned D, original, MIT.

A guide for diagnosing and validating Ansible playbooks and roles. Playbooks describe automation steps, roles organize reusable Ansible code, and idempotence means repeated runs produce the same intended result.

In plain words
What is it for?
It helps find playbook failures, inspect variables and task results, test changes, check code quality, and verify that repeated runs remain safe.
Why use it?
It provides a defined investigation process using logs, verbosity, check mode, ansible-lint, and Molecule instead of relying on trial and error.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the ansible-skills plugin — 11 skills shipped together

Good fit It helps find playbook failures, inspect variables and task results, test changes, check code quality, and verify that repeated runs remain safe.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stoleas/ansible-skills/ansible-troubleshooter
Install

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.

Any agent
npx skills add stoleas/ansible-skills --skill ansible-troubleshooter
Clone the repo
git clone --depth 1 https://github.com/stoleas/ansible-skills

Made for: Claude Code.

Or install ansible-skills, the plugin that ships this one along with the rest of its 11 skills.

Wrote 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.

agentmods badge for ansible-troubleshooter

README.md
[![agentmods](https://agentmods.dev/badge/skills/stoleas/ansible-skills/ansible-troubleshooter/github.svg)](https://agentmods.dev/skills/stoleas/ansible-skills/ansible-troubleshooter)
Your own site
<a href="https://agentmods.dev/skills/stoleas/ansible-skills/ansible-troubleshooter"><img src="https://agentmods.dev/badge/skills/stoleas/ansible-skills/ansible-troubleshooter/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.

agentmods 80×15 button for ansible-troubleshooter

Your own site · 80×15
<a href="https://agentmods.dev/skills/stoleas/ansible-skills/ansible-troubleshooter"><img src="https://agentmods.dev/badge/skills/stoleas/ansible-skills/ansible-troubleshooter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,320 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00128 $0.04320
Opus 5 $0.00064 $0.02160
Sonnet 5 $0.00026 $0.00864
Haiku 4.5 $0.00013 $0.00432

Measured 12d ago against content hash be881f55d6ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade D, and why

ansible-troubleshooter scanned grade D with 2 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- become/sudo operations

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

ssh-add ~/.ssh/id_rsa
skills/ansible-troubleshooter/SKILL.md · 746 lines

How it starts

The opening of the file, as written. The whole thing — 746 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ansible Troubleshooter Skill

Debug, troubleshoot, and validate Ansible playbooks and roles using Red Hat CoP best practices, ansible-lint, and Molecule.

Troubleshooting Workflow

  1. Identify the issue - Understand what's failing and where
  2. Gather information - Use verbosity, logs, debug module
  3. Isolate the problem - Test specific tasks, use check mode
  4. Apply the fix - Make targeted changes
  5. Validate - Ensure fix works and doesn't break other things
  6. Test idempotence - Verify playbook can run multiple times

Ansible Verbosity Levels

Use -v flags to get more information about execution:

-v (Basic Verbosity)

Shows task results and return values.

ansible-playbook -v playbook.yml

When to use:

  • See what tasks are doing
  • View task return values
  • Understand task outcomes

Output includes:

  • Task results (ok/changed/failed)
  • Return values from modules
  • Basic execution flow

-vv (More Verbosity)

Shows task input parameters.

ansible-playbook -vv playbook.yml

When to use:

  • See what parameters are being passed to tasks
  • Debug variable interpolation issues
  • Understand why a task behaves unexpectedly

Output includes:

  • All -v output
  • Task input parameters
  • Variable values being used

-vvv (Connection Debug)

Shows connection debugging information.

ansible-playbook -vvv playbook.yml

When to use:

  • Debug SSH connection issues
  • Investigate authentication problems
  • Troubleshoot privilege escalation (become)
  • See what's happening at the transport layer

Output includes:

  • All -vv output
  • SSH connection details
  • Authentication attempts
  • File transfers
  • become/sudo operations

-vvvv (Maximum Verbosity)

Shows SSH protocol details and internal Ansible workings.

ansible-playbook -vvvv playbook.yml

When to use:

  • Deep protocol debugging
  • Understanding Ansible internals
  • Reporting bugs to Ansible developers
  • Last resort for complex issues

Read the full file on GitHub · 746 lines

Files

What ships with it

3 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.

Changes

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.

  1. 12d ago First seen · 746 lines · 128 tokens per session scan D be881f55d6ed

Subscribe to this mod's changes

ansible-troubleshooter is a skill published in the GitHub repository stoleas/ansible-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 128 tokens to every session and 4,320 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens