update-conf — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited update-conf (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Update an existing ansible.cfg with targeted changes. Always shows a diff and waits for confirmation before writing.
Locate the ansible.cfg via discovery (references/discovery.md).
Read the full ansible.cfg content.
Before displaying any content or diff, scan every line for credential-like values:
password, secret, token, key, pass, credential, or vault_password_file{{ vault_* }}), empty, or Nonepassword = ***REDACTED*** ⚠ Warning: N line(s) with credential-like values were redacted from this display.
Review the file directly before applying changes.Apply the requested change:
host_key_checking = False → must have a comment explaining whyvault_password_file → add chmod reminder commentkey = value with spaces around =collections_path in newly generated examples while preserving existing intent in older files--- ansible.cfg (original)
+++ ansible.cfg (proposed)
@@ -8,6 +8,9 @@
forks = 10
timeout = 30
+
+# Fact caching: redis (shared across controller nodes; configure auth via REDIS_URL or vault)
+fact_caching = redis
+fact_caching_connection = redis://:{{ vault_redis_password }}@cache.internal:6379/0
+fact_caching_timeout = 86400Then ask: "Apply this change? (yes/no)"
echo "Updated: $(realpath ansible.cfg)"Suggest next step:
Next step: Validate with `ansible --version` to confirm the config is loaded
or run /ansible-designer:review-conf to check for remaining issues.| Change requested | How to handle |
|---|---|
| Set a key in an existing section | Find the section, update the key value; add if not present |
| Add a new section | Append section at end of file with appropriate keys |
| Enable fact caching | Set fact_caching, fact_caching_connection, fact_caching_timeout in [defaults] |
| Add vault_identity_list | Add/update vault_identity_list in [defaults]; show example format |
| Change callback plugins | Update callbacks_enabled in [defaults]; warn if awx_display is being added |
| Enable pipelining | Add pipelining = True to [ssh_connection]; add sudoers note comment |
| Change stdout_callback | Update stdout_callback in [defaults] |
| Set forks | Update forks in [defaults]; add RAM note if value > 50 |
| Remove a setting | Remove the line (and its comment if inline or immediately preceding) |
| Comment out a setting | Prefix line with # and add a note explaining why it's disabled |
host_key_checking = True to False without adding a justification comment.vault_password_file, add a comment reminding about chmod 600.forks > 100, warn: "Each fork uses ~100MB RAM — ensure the controller has sufficient memory."=).host_key_checking, become, transport, vault_password_file, callback or stdout plugins), always add an inline comment explaining the security implication of the change.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.