Skip to content
TrustedSkillsbeta
Back to all skills

Sast Configuration

Checked
wshobson·vlatest·devops·MIT

This skill automates Sast configuration by generating YAML files based on your project's dependencies, streamlining security scanning setup.

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 wshobson/agents --skill sast-configuration -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

wshobson

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 wshobson/agents at 46891e7e60.

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

Commit
46891e7e60
Manifest
plugins/security-scanning/skills/sast-configuration/SKILL.md
Scanned
1 file, 180 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 sast-configuration skill enables AI agents to configure and manage Static Application Security Testing (SAST) tools. It provides capabilities such as setting up scan configurations, defining rulesets, and integrating with CI/CD pipelines for automated security testing.

When to use it

  • When configuring SAST tools like SonarQube or Fortify within a development workflow.
  • To define custom security rules for code analysis in a project-specific context.
  • During the setup of continuous integration environments that require automated vulnerability scanning.

Key capabilities

  • Configure scan parameters and thresholds for SAST tools.
  • Define and apply custom rule sets for static analysis.
  • Integrate with CI/CD pipelines to automate security testing processes.

Example prompts

  • "Configure SonarQube to analyze JavaScript files in the src directory."
  • "Set up a Fortify scan with custom rules for OWASP Top 10 vulnerabilities."
  • "Integrate SAST into our GitHub Actions pipeline for every pull request."

Tips & gotchas

  • Ensure that the AI agent has access to the necessary SAST tool APIs or configuration files.
  • Custom rule sets may require domain-specific knowledge to define effectively.