Back to catalog
Static reviewDevelopment

Skill dossier

integrating-sast-into-github-actions-pipeline

Source declaration

Integrates CodeQL and Semgrep SAST scanning into GitHub Actions, covering scans on pull requests/pushes, rule tuning to cut false positives, SARIF upload to GitHub Advanced Security, and merge-blocking quality gates for high-severity findings. Use when adding automated code vulnerability detection to CI, enforcing consistent SAST org-wide, or producing SOC 2/PCI DSS/NIST SSDF compliance evidence.

The author's original description, preserved in English. It describes intent, not verified performance.

Integrates CodeQL and Semgrep SAST scanning into GitHub Actions, covering scans on pull requests/pushes, rule tuning to cut false positives, SARIF upload to GitHub Advanced Security, and merge-blocking quality gates for high-severity findings. Use when adding automated code vulnerability detection to CI, enforcing consistent SAST org-wide, or producing SOC 2/PCI DSS/NIST SSDF compliance evidence.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Integrates CodeQL and Semgrep SAST scanning into GitHub Actions, covering scans on pull requests/pushes, rule tuning to cut false positives, SARIF upload to GitHub Advanced Security, and merge-blocking quality gates for high-severity findings. Use when adding automated code vulnerability detection to CI, enforcing consistent SAST org-wide, or producing SOC 2/PCI DSS/NIST SSDF compliance evidence. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L46]
  • Step 1: Configure CodeQL Analysis Workflow [Source statement; provisional, not tested. Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L48]
  • Step 2: Add Semgrep Scanning for Custom Rules [Source statement; provisional, not tested. Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L97]
  • Step 3: Create Custom Semgrep Rules for Organization Patterns [Source statement; provisional, not tested. Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L146]
  • Step 4: Establish Quality Gates with Branch Protection [Source statement; provisional, not tested. Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L194]
  • Step 5: Tune and Suppress False Positives [Source statement; provisional, not tested. Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L207]
  • Step 6: Aggregate and Report Findings [Source statement; provisional, not tested. Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L238]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L1-L25]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
56.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/integrating-sast-into-github-actions-pipeline/assets/template.mdReference4.7 KB
skills/integrating-sast-into-github-actions-pipeline/LICENSEOther11 KB
skills/integrating-sast-into-github-actions-pipeline/references/api-reference.mdReference1.4 KB
skills/integrating-sast-into-github-actions-pipeline/references/standards.mdReference2.9 KB
skills/integrating-sast-into-github-actions-pipeline/references/workflows.mdReference5.2 KB
skills/integrating-sast-into-github-actions-pipeline/scripts/agent.pyScript5.7 KB
skills/integrating-sast-into-github-actions-pipeline/scripts/process.pyScript13.4 KB
skills/integrating-sast-into-github-actions-pipeline/SKILL.mdInstruction11.9 KB

SKILL.md frontmatter

{
  "name": "integrating-sast-into-github-actions-pipeline",
  "description": "Integrates CodeQL and Semgrep SAST scanning into GitHub Actions, covering scans on pull requests/pushes, rule tuning to cut false positives, SARIF upload to GitHub Advanced Security, and merge-blocking quality gates for high-severity findings. Use when adding automated code vulnerability detection to CI, enforcing consistent SAST org-wide, or producing SOC 2/PCI DSS/NIST SSDF compliance evidence.",
  "domain": "cybersecurity",
  "subdomain": "devsecops",
  "tags": [
    "devsecops",
    "cicd",
    "sast",
    "codeql",
    "semgrep",
    "secure-sdlc"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "GV.SC-07",
    "ID.IM-04",
    "PR.PS-04"
  ],
  "mitre_attack": [
    "T1195",
    "T1554",
    "T1059.004"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Configure CodeQL Analysis Workflow

    Source-described action candidate under “Step 1: Configure CodeQL Analysis Workflow”; not verified execution.

  4. 04
    Action

    Create a CodeQL workflow that runs on pull requests and on a weekly schedule to catch vulnerabilities in existing code.

    Source-described action candidate under “Step 1: Configure CodeQL Analysis Workflow”; not verified execution.

  5. 05
    Action

    Step 2: Add Semgrep Scanning for Custom Rules

    Source-described action candidate under “Step 2: Add Semgrep Scanning for Custom Rules”; not verified execution.

  6. 06
    Action

    Step 3: Create Custom Semgrep Rules for Organization Patterns

    Source-described action candidate under “Step 3: Create Custom Semgrep Rules for Organization Patterns”; not verified execution.

Inspect all extracted workflow candidates (26 candidate steps)
  1. 07
    Output

    Write organization-specific rules to catch patterns unique to your codebase, such as deprecated internal APIs or insecure configuration patterns.

    Source-described output candidate under “Step 3: Create Custom Semgrep Rules for Organization Patterns”; not verified execution.

  2. 08
    Decision

    Step 4: Establish Quality Gates with Branch Protection

    Source-described decision candidate under “Step 4: Establish Quality Gates with Branch Protection”; not verified execution.

  3. 09
    Action

    Step 5: Tune and Suppress False Positives

    Source-described action candidate under “Step 5: Tune and Suppress False Positives”; not verified execution.

  4. 10
    Output

    Step 6: Aggregate and Report Findings

    Source-described output candidate under “Step 6: Aggregate and Report Findings”; not verified execution.

  5. 11
    Action

    Use the GitHub Security Overview dashboard and configure notifications for security alerts across repositories.

    Source-described action candidate under “Step 6: Aggregate and Report Findings”; not verified execution.

  6. 12
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  7. 13
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  8. 14
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  9. 15
    Action

    Configure CodeQL with a matrix strategy covering Python, JavaScript, and Go languages

    Source-described action candidate under “Scenario: Monorepo with Multiple Languages Needs Unified SAST”; not verified execution.

  10. 16
    Action

    Add Semgrep with `--config auto` to detect language automatically and apply relevant rulesets

    Source-described action candidate under “Scenario: Monorepo with Multiple Languages Needs Unified SAST”; not verified execution.

  11. 17
    Action

    Create path-based triggers so only changed language directories trigger their respective scans

    Source-described action candidate under “Scenario: Monorepo with Multiple Languages Needs Unified SAST”; not verified execution.

  12. 18
    Input

    Upload all SARIF results to GitHub Security tab with unique categories per tool and language

    Source-described input candidate under “Scenario: Monorepo with Multiple Languages Needs Unified SAST”; not verified execution.

  13. 19
    Decision

    Set branch protection requiring all SAST jobs to pass before merge

    Source-described decision candidate under “Scenario: Monorepo with Multiple Languages Needs Unified SAST”; not verified execution.

  14. 20
    Action

    Schedule weekly full-repository scans to catch issues in unchanged code from newly published CVE patterns

    Source-described action candidate under “Scenario: Monorepo with Multiple Languages Needs Unified SAST”; not verified execution.

  15. 21
    Output

    Export all current alerts and categorize them as true positive, false positive, or informational

    Source-described output candidate under “Scenario: Reducing Alert Fatigue from High False Positive Rate”; not verified execution.

  16. 22
    Action

    Create a custom CodeQL config excluding noisy query IDs that produce the most false positives

    Source-described action candidate under “Scenario: Reducing Alert Fatigue from High False Positive Rate”; not verified execution.

  17. 23
    Output

    Write `.semgrepignore` patterns for test files, generated code, and vendored dependencies

    Source-described output candidate under “Scenario: Reducing Alert Fatigue from High False Positive Rate”; not verified execution.

  18. 24
    Action

    Establish a weekly triage meeting where security and development leads review new rule additions

    Source-described action candidate under “Scenario: Reducing Alert Fatigue from High False Positive Rate”; not verified execution.

  19. 25
    Action

    Track false positive rate as a metric and target below 15% for developer trust

    Source-described action candidate under “Scenario: Reducing Alert Fatigue from High False Positive Rate”; not verified execution.

  20. 26
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

22 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

9 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 9 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

13 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 13 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/integrating-sast-into-github-actions-pipeline/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/integrating-sast-into-github-actions-pipeline/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/integrating-sast-into-github-actions-pipeline
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.