agentleFS
Sign inStart free
Quad4-SoftwareQuad4-Software/skills/.agents/skills/sast/SKILL.md

sast

Skill1 starsChanged 43 days ago0BSDView on GitHub

This skill covers free and open-source local static analysis, linting, secret scanning, dependency scanning, and IaC scanning tools as of October 2026: ruff, bandit, opengrep, semgrep CE, gosec, staticcheck, golangci-lint, ESLint v10, oxlint, biome, gitleaks, trufflehog, detect-secrets, osv-scanner, trivy, grype, syft, cargo-audit, cargo-deny, checkov, hadolint, kube-linter, conftest, shellcheck, shfmt, codeql CLI, zizmor, and meta runners like pre-commit and MegaLinter. Use it when picking a scanner, wiring pre-commit or CI gates, or auditing a repo locally.

2 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. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read this file for the landscape and decision rules.

    line 25
  2. Distinctive:

    Verify versions against the linked release pages.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

When to use this skill

  • You are picking a linter or SAST tool for a language.
  • You are scanning a repo for secrets, vulnerable deps, or bad IaC.
  • You are building a pre-commit or CI scanning gate.
  • You need to know which tools run fully offline vs need a DB or registry.

How to use

  1. Read this file for the landscape and decision rules.
  2. Load a reference file by scope: references/python.md for ruff, bandit, and the Python type-checker wars. references/scanners.md for secrets, SCA, IaC, shell, Rust, Go, and JS tools with versions and offline notes. references/multi.md for opengrep vs semgrep, codeql licensing, SonarQube, MegaLinter, and pre-commit glue.
  3. Verify versions against the linked release pages. These tools ship weekly.

Examples

  • "Which tools should gate this repo's pre-commit?"
  • "Semgrep or opengrep for a self-hosted scan?"
  • "Scan this Dockerfile and the k8s manifests locally."

Local security tooling landscape

Decision rules

  • Python: ruff (S rules port most of bandit) + a type checker (basedpyright or pyrefly stable, ty beta, mypy 2.x). Bandit is redundant if ruff S is on.
  • Multi-language SAST: opengrep (LGPL, fully offline with local rules, cross-function taint, cross-file in v2 alphas) or semgrep CE (registry rules need network and are under a restrictive license).
  • Go: go vet + staticcheck + gosec + govulncheck (reachability cuts false positives). golangci-lint v2.x wraps most of them.
  • JS/TS: ESLint v10 (flat config only) or oxlint (type-aware via tsgolint on TypeScript 7). Biome if you want one binary for lint + format.
  • Secrets: gitleaks for offline speed (feature-frozen, fine), trufflehog when you need live verification (AGPL, needs network to verify), detect-secrets for baseline workflows.
  • Dependencies: osv-scanner (offline DB mode) or trivy fs/repo. npm audit alone is a floor, not a strategy. govulncheck and reach- ability analysis remove ~85% of SCA noise.
  • IaC: checkov (Terraform/K8s/Helm/Dockerfile), trivy config (tfsec is absorbed), KICS for breadth. Terrascan is archived.
  • Containers: hadolint for Dockerfiles, trivy image or grype for contents, kube-linter for manifests/Helm.
  • Shell: shellcheck + shfmt.
  • CI security: zizmor for GitHub Actions (offline mode, SARIF).
  • Orchestration: pre-commit for local gates, MegaLinter for CI fan-out (v10.x, images only on ghcr.io since v9.5).
  • CodeQL: deep but the engine is proprietary - free only for public repos, OSS research, and query testing. Not for private CI without GitHub Code Security.

Output plumbing

Most tools emit SARIF (ruff --output-format=sarif, gosec -fmt sarif, opengrep, zizmor, trivy, checkov). Pipe SARIF into GitHub code scanning or a local aggregator. --baseline mechanisms exist in detect-secrets and gitleaks for legacy-repo adoption.

Reference files

  • references/python.md
  • references/scanners.md
  • references/multi.md

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