- Home
- Skills
- DevOps & Cloud
- Ansible Safety Check
More screenshots
Works with the AI Agents you already use
Ansible Safety Check
It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach.
$5
Ansible Safety Check
Example session with this skill installed
Check this project with ansible-safety-check.
- Read your context and instructions
- Compiled the ansible safety check
$ python3 scripts/check_ansible.py examples/risky
BLOCK site.yml:5 A01 HARDCODED_SECRET
db_password=<redacted, 19 chars>
Why: A password, token or key is written as plain text in vars, an inventory or role vars file, or a module parameter. Anyone who can read the repository can use it, and it stays in git history.
Safer: Rotate it, then keep it in an Ansible Vault file (ansible-vault encrypt_string) or a secrets lookup, and refer to it as "{{ vault_db_password }}".
BLOCK site.yml:12 A02 CURL_PIPE_TO_SHELL
REVIEW ansible.cfg:4 A16 HOST_KEY_CHECKING_DISABLED
REVIEW site.yml:10 A14 PACKAGE_STATE_LATEST
REVIEW site.yml:19 A13 WORLD_WRITABLE_MODE
REVIEW site.yml:20 A12 CERTIFICATE_CHECK_DISABLED
REVIEW site.yml:25 A11 SECRET_WITHOUT_NO_LOG
REVIEW site.yml:31 A15 GIT_CHECKOUT_NOT_PINNED
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 2 files, 2 with Ansible content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A password: "{{ db_password }}" task without no_log: true prints the password in Ansible's output and in your CI logs, and a db_password written in group_vars sits in git history for good. This skill finds those and six other risky Ansible settings, and tells you how to fix each one.
Your agent runs a scanner on your playbooks, roles (tasks, handlers, defaults, vars), inventories (YAML or INI), group_vars and host_vars files, and ansible.cfg. It reads blocks, handlers, short and full module names (apt or ansible.builtin.apt), key=value arguments and args:, and treats !vault values and templates as safe. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secret values are never printed.
What it checks
BLOCK
- A01: a password, token or key in plain text in vars or a module parameter
- A02: curl or wget piped into a shell in a shell, command or raw task
REVIEW
- A11: a secret passed to a task without no_log: true
- A12: validate_certs: no or curl -k
- A13: a world-writable mode such as 0777
- A14: state: latest on package tasks
- A15: a git checkout of a branch instead of a tag or commit
- A16: SSH host key checking turned off
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example playbook, and the real report the scanner produces on the risky one
Limits It reads YAML text and does not run Jinja, resolve variables from other files, or follow include_tasks and roles from collections. NOT FLAGGED is not a guarantee.
Static check of Ansible YAML. Jinja is not evaluated, and included tasks and collection roles are not followed. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example playbook includes a clearly fake, inert password (not-a-real-password) for the scanner to find.