Security Auditor
CheckedIdentifies potential vulnerabilities in fan configurations and access controls using Charon's data and security best practices.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add zhaono1/agent-playbook --skill security-auditor -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
charon-fan
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned charon-fan/agent-playbook at be7a9d7d17.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- be7a9d7d17
- Manifest
- skills/security-auditor/SKILL.md
- Scanned
- 7 files, 356 lines
About this skill
The security-auditor skill from charon-fan/agent-playbook provides a framework for AI agents to systematically evaluate system safety and compliance. It enables automated scanning of configurations, logs, and policies to identify potential vulnerabilities or misconfigurations before they are exploited.
When to use it
- Pre-deployment validation: Run audits on new infrastructure setups or code changes before they go live to catch errors early.
- Compliance verification: Check if current system states adhere to internal security policies or external regulatory standards like GDPR or HIPAA.
- Incident response analysis: Investigate recent security alerts by auditing logs and access patterns to determine the root cause of a breach.
- Routine maintenance checks: Schedule periodic automated reviews of firewall rules, user permissions, and encryption settings to ensure ongoing protection.
Key capabilities
- Automated discovery of security misconfigurations across various system components.
- Generation of detailed audit reports highlighting specific risks and remediation steps.
- Integration with existing agent playbooks to trigger immediate corrective actions upon finding critical issues.
- Support for custom rule sets tailored to specific organizational security requirements.
Example prompts
- "Run a full security audit on our production database cluster and summarize any high-severity findings."
- "Audit the current IAM policies to identify users with excessive privileges that violate our least-privilege principle."
- "Check the latest deployment logs for signs of unauthorized access attempts or failed authentication events."
Tips & gotchas
Ensure your AI agent has read-only access to the systems being audited to prevent accidental disruption during the scan. For complex environments, combine this skill with manual review steps, as automated tools may occasionally flag false positives that require human context to resolve.