Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    sast configuration governance

    1

    Plan, configure, and govern SAST programmes with scanner-agnostic designs and CI/CD quality gates.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    sast configuration governance

    sast configuration governance

    Example session with this skill installed

    I need to roll out SAST for a TypeScript and Go project using GitHub Actions. We want to start with advisory warnings and move to blocking PRs for high-severity issues in 3 months.

    • Read your context and instructions
    • Compiled the sast configuration governance

    I have designed a phased SAST rollout plan for your TypeScript and Go project. The strategy focuses on establishing a baseline before moving to active enforcement.

    SAST Implementation Plan: GitHub Actions

    PhaseDurationEnforcement ModeObjective
    Phase 1: BaselineWeeks 1-4Advisory (Non-blocking)Identify existing vulnerabilities and suppress legacy technical debt.
    Phase 2: TriageWeeks 5-8Warning (PR Comment)Educate developers on new findings without stopping the build.
    Phase 3: EnforcementMonth 3+Blocking (Hard Gate)Block PRs containing new High/Critical vulnerabilities.

    Technical Configuration Design

    
    # GitHub Actions Workflow Snippet (Phase 1/2)
    name: Security Scan
    on:
      pull_request:
        branches: [main]
    jobs:
      sast_scan:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v4
          - name: Initialize Scanner
            # Placeholder for chosen tool (e.g., CodeQL or Semgrep)
            run: echo "Initializing scan for TypeScript/Go..."
          - name: Perform Analysis
            # Continue on error during advisory phases
            continue-on-error: true
            run: |
              scan-tool --severity high --format sarif --output results.sarif
          - name: Upload Results
            uses: github/codeql-action/upload-sarif@v2
            with:
              sarif_file: results.sarif
    

    Quality Gate Policy

    • Critical/High: Must be remediated or formally suppressed with a documented false-positive reason before Phase 3.
    • Medium/Low: Logged for technical debt backlog; no blocking enforcement planned.
    • SLA: 14 days for Critical, 30 days for High findings post-Phase 3.

    Next steps

    1. Select a specific scanner (Semgrep or CodeQL recommended) to generate the final workflow syntax.
    2. Define the formal exception process for business-critical overrides.
    3. Run an initial baseline scan to quantify the current vulnerability backlog.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Integrating Static Application Security Testing (SAST) often fails due to high false-positive rates, broken CI/CD pipelines, or lack of clear enforcement policies. Security teams struggle to define meaningful quality gates without disrupting developer velocity.

    What it does

    • Generates scanner-agnostic SAST implementation plans for new or existing repositories.
    • Defines quality gate policies and severity thresholds based on risk tolerance and rollout stage.
    • Designs CI/CD integration workflows for tools like GitHub Actions, GitLab CI, or Jenkins.
    • Drafts governance rules for false-positive handling, suppression workflows, and remediation SLAs.
    • Produces developer-facing guidance and executive maturity reports for security programmes.

    Frameworks & tools

    Supports configuration design for Semgrep, SonarQube, CodeQL, and GitHub Advanced Security. Compatible with standard CI/CD platforms and SARIF-compliant reporting tools.

    Why this beats prompting it yourself

    General-purpose models often hallucinate scanner commands or recommend "blocking" gates that break production builds immediately. This skill enforces a phased rollout approach and insists on false-positive governance, preventing the common pitfalls of automated security tooling.

    Use cases

    • Rollout SAST for a polyglot microservices portfolio with phased enforcement.
    • Migrate from a legacy security scanner to a modern, developer-centric tool.
    • Audit existing SAST configurations to reduce noise and improve signal-to-noise ratios.
    • Standardize security quality gates across multiple engineering squads.

    Known limitations

    Cannot execute live API calls to your security platform or push configuration files directly to your VCS. It requires the user to specify the target scanner for tool-specific syntax.

    Requires user to specify the target scanner for tool-specific commands. Cannot perform live repository or pipeline modifications. Does not handle DAST or secret scanning without a SAST component.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    No special permissions declared or detected

    Listed2 months ago

    What's inside

    Frequently Asked Questions

    This skill provides a structured blueprint for SAST implementation, focusing on scanner-agnostic designs, severity-based quality gates, and standardized governance to reduce developer friction and false positives.

    It supports configuration design for major industry tools including Semgrep, SonarQube, CodeQL, and GitHub Advanced Security, ensuring your security gates remain consistent regardless of the underlying scanner.

    You will receive a specialized AI agent workflow that generates actionable implementation plans, governance documentation, remediation SLAs, and phased rollout strategies tailored to your technical stack.

    Yes, it includes specialized logic for defining suppression workflows and false-positive handling rules, ensuring that your security team can maintain high-signal reporting without blocking valid code changes.

    Because security tools and CI/CD standards evolve, this skill receives periodic updates to incorporate the latest best practices for SARIF-compliant reporting and emerging scanner features.

    No, for security and compliance reasons, the skill generates the configuration logic and integration steps which you then manually review and apply to your specific CI/CD environment or VCS.

    New in Security