Skip to content
TrustedSkillsbeta
Back to all skills

Skills Security Audit

Listed
agentnode-dev·vlatest·security

Helps with security, auditing as part of implementing security and authentication workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add agentnode-dev/skills-security-audit --skill skills-security-audit -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

agentnode-dev

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 2 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 credential access: failed

    Touches credential material in 2 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/skills-security-audit/SKILL.md:125SSH private keys or config
      | 3 | skill-c | 6.0 | 🔴 DANGEROUS | 2 | 1 | 1 | [DE-001] Reads ~/.ssh/id_rsa |
    • skills/skills-security-audit/SKILL.md:136SSH private keys or config
      | [DE-001] CRITICAL | lib/init.sh:14 | Reads `~/.ssh/id_rsa` | Remove sensitive file access |

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 1 place.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • skills/skills-security-audit/SKILL.md:126remote script piped into a shell
      | 4 | skill-d | 8.2 | 🟣 MALICIOUS | 3 | 2 | 0 | [CE-003] curl | sh execution |

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

  • Pinned to a commit: passed

    Scanned agentnode-dev/skills-security-audit at 24b005b16a.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
24b005b16a
Manifest
skills/skills-security-audit/SKILL.md
Scanned
2 files, 782 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill performs security audits, identifying potential vulnerabilities and weaknesses in systems or applications. It analyzes configurations, code, and network traffic to pinpoint areas of risk. The audit results are presented with recommendations for remediation, improving overall security posture.

When to use it

  • Pre-deployment checks: Before launching a new application or system, run an audit to identify and fix vulnerabilities early on.
  • Compliance assessments: Use the skill to verify adherence to specific security standards (e.g., SOC 2, HIPAA).
  • Post-incident analysis: After a security incident, conduct an audit to determine root causes and prevent recurrence.
  • Periodic reviews: Regularly schedule audits to ensure ongoing security health and identify newly introduced risks.

Key capabilities

  • Vulnerability scanning
  • Configuration review
  • Network traffic analysis
  • Remediation recommendations

Example prompts

  • "Perform a security audit of my web application, focusing on SQL injection vulnerabilities."
  • "Can you analyze the configuration of this server and identify any potential misconfigurations?"
  • "Conduct a network traffic analysis to detect suspicious activity."

Tips & gotchas

The effectiveness of this skill depends on providing accurate and complete information about the system or application being audited. Ensure proper access permissions are granted for thorough assessment.