Skip to content
TrustedSkillsbeta
Back to all skills

Security Scanning

Checked
bobmatnyc·vlatest·security·MIT

Identifies vulnerabilities in code, configurations, and networks using automated scanning tools and reports potential risks.

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 bobmatnyc/claude-mpm-skills --skill security-scanning -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

bobmatnyc

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 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 bobmatnyc/claude-mpm-skills at 718070a7d6.

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

Commit
718070a7d6
Manifest
universal/security/security-scanning/SKILL.md
Scanned
8 files, 561 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

The Security Scanning skill enables an AI agent to identify vulnerabilities in code, configurations, and networks using automated scanning tools. It focuses on quickly identifying critical security risks and provides guidance for remediation. The tool prioritizes a “fail fast” approach with secrets management and emphasizes automating updates of dependencies. Static Application Security Testing (SAST) is initiated at a high-signal level, with the intention to gradually expand coverage over time.

When to use it

  • To quickly identify and remediate exposed secrets within a codebase or environment.
  • When managing software dependencies and ensuring they are up-to-date to prevent vulnerabilities.
  • As part of an automated build process to perform initial security scans (SAST).
  • To prioritize and address critical/high severity findings first.

Key capabilities

  • Secrets management with a focus on rapid failure and rotation upon exposure.
  • Automated dependency updates for vulnerability mitigation.
  • Static Application Security Testing (SAST) implementation, starting with high-signal areas.
  • Exception handling process requiring justification, ownership, and expiry dates.

Example prompts

  • "Scan this repository for exposed secrets."
  • "What are the critical dependencies that need updating?"
  • "Run a SAST scan on my codebase and prioritize findings."

Tips & gotchas

  • Secrets management requires immediate action upon detection; rotation is crucial.
  • Dependency updates should be automated to ensure consistent security posture.
  • SAST scans are initially focused on high-signal areas, with plans for broader coverage over time.