agentleFS
Sign inStart free
kumaran-iskumaran-is/claude-code-onboarding/.claude/skills/sast-configuration/SKILL.md

sast-configuration

Skill35 starsChanged 6 months agoMITView on GitHub

Static Application Security Testing (SAST) configuration skill. Use when setting up security scanning, configuring Semgrep rules, running SAST in CI/CD, reviewing SAST findings, or writing custom security rules. Triggers: SAST, static analysis, Semgrep, Bandit, ESLint security, code scanning, vulnerability detection, security scan setup.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/semgrep-custom-rules.md before writing or modifying any SAST configuration.

    line 17
  2. Distinctive:

    If a scanner is not installed, report the install command from the tool config reference rather than skipping the scan silently.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Iron Law: NO SAST CONFIGURATION WITHOUT READING THE CUSTOM RULES FILE FIRST

Read references/semgrep-custom-rules.md before writing or modifying any SAST configuration.

When to Use

  • Setting up scanning for a new service → tool selection + config templates
  • Writing or modifying Semgrep rules → custom rules reference
  • Integrating SAST into CI/CD → GitHub Actions example in tool config
  • Triaging SAST findings → risk scoring and false positive suppression

Process

  1. Detect languages — Check for pom.xml (Java), package.json (TS), pyproject.toml (Python), pubspec.yaml (Dart)
  2. Load custom rules — Read references/semgrep-custom-rules.md for project-specific rules already in place
  3. Select tools — Java → SpotBugs + Semgrep; TS/Angular/NestJS → ESLint security + Semgrep; Python → Bandit + Semgrep; Dart → dart analyze
  4. Configure — See references/sast-tool-config.md for config file templates and CI/CD step
  5. Run and triage — Execute /security-sast [path], classify findings, suppress false positives per the suppression patterns in tool config

References

FileContent
references/semgrep-custom-rules.md10 custom Semgrep rules for Java/TS/Python, usage, suppression syntax
references/sast-tool-config.mdTool comparison matrix, config templates (Bandit/.bandit, ESLint, dart analyze, Semgrep CI), risk scoring thresholds

Error Handling

If a scanner is not installed, report the install command from the tool config reference rather than skipping the scan silently.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free