Agent skill

Implementing API Security Testing With 42crunch

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Implements API security testing on the 42Crunch platform, combining API Audit for static analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability testing, and API Protect for…

Apache-2.0Auto-check passedSecurity

Install Implementing API Security Testing With 42crunch

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-api-security-testing-with-42crunch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-api-security-testing-with-42crunch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementing-api-security-testing-with-42crunch .claude/skills/implementing-api-security-testing-with-42crunch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
implementing-api-security-testing-with-42crunch
GitHub stars
34k
Token cost
~2.8k tokens
SKILL.md length
574 words
Files
4 (incl. scripts, references)
Skills in repo
637
Repo updated
First seen
Licence
Apache-2.0

At a glance

Implements API security testing on the 42Crunch platform, combining API Audit for static analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability testing, and API Protect for…

  • Works in 5 steps: Install the 42Crunch extension from the… → Open an OpenAPI specification file (YAML… → Click the security audit icon in the… → …
  • Shift-left testing APIs for OWASP API Security Top 10 vulnerabilities
  • SKILL.md covers Overview, When to Use, Prerequisites and Core Concepts, plus 3 more sections
  • Runs Python scripts from its folder; calls npm; needs CRUNCH_TOKEN and CRUNCH_API_TOKEN

What it does

Implementing API Security Testing With 42crunch is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Implements API security testing on the 42Crunch platform, combining API Audit for static analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability testing, and API Protect for runtime threat prevention, integrated into CI/CD pipelines and IDEs. Use when shift-left testing APIs for OWASP API Security Top 10 vulnerabilities or setting up 42Crunch audit and conformance scanning.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).

It sits in Security, covering CI/CD, OpenAPI specifications and Static analysis and SAST. It works with OpenAPI and Visual Studio Code. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Shift-left testing APIs for OWASP API Security Top 10 vulnerabilities
  • Setting up 42Crunch audit and conformance scanning

Example prompts

  • “Use the implementing-api-security-testing-with-42crunch skill to implement API security testing on the 42Crunch platform, combining API Audit for…”
  • “/implementing-api-security-testing-with-42crunch”

Requirements

  • Python 3
  • Node.js
  • A credential in API_TOKEN
  • A credential in CRUNCH_TOKEN

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Install the 42Crunch extension from the VS Code marketplace
  2. Open an OpenAPI specification file (YAML or JSON)
  3. Click the security audit icon in the editor toolbar
  4. Review the security score (0-100) and individual findings
  5. Address issues using the inline remediation guidance

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • 42crunch.com
    • docs.42crunch.com
    • learn.microsoft.com
    • owasp.org
    • plugins.jenkins.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CRUNCH_TOKEN
    • CRUNCH_API_TOKEN
    • API_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implementing API Security Testing With 42crunch loads about 2.8k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 574 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 574 words, ~2,765 tokens.

Download SKILL.mdSave it as .claude/skills/implementing-api-security-testing-with-42crunch/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
implementing-api-security-testing-with-42crunch
description
Implements API security testing on the 42Crunch platform, combining API Audit for static analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability testing, and API Protect for runtime threat prevention, integrated into CI/CD pipelines and IDEs. Use when shift-left testing APIs for OWASP API Security Top 10 vulnerabilities or setting up 42Crunch audit and conformance scanning.
domain
cybersecurity
subdomain
api-security
tags
api-security, 42crunch, openapi, api-audit, api-scan, conformance-testing, shift-left, ci-cd-security, owasp-api-top-10
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
PR.PS-01, ID.RA-01, PR.DS-10, DE.CM-01
mitre_attack
T1190, T1059.007, T1552.001

Implementing API Security Testing with 42Crunch

Overview

42Crunch is an API security platform that combines Shift-Left security testing with Shield-Right runtime protection. It provides API Audit for static security analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability detection, and API Protect for real-time threat prevention. The platform integrates into CI/CD pipelines and IDEs to identify OWASP API Security Top 10 vulnerabilities before and after deployment.

When to Use

  • When deploying or configuring implementing api security testing with 42crunch capabilities in your environment
  • When establishing security controls aligned to compliance requirements
  • When building or improving security architecture for this domain
  • When conducting security assessments that require this implementation

Prerequisites

  • 42Crunch platform account (free tier available for evaluation)
  • OpenAPI Specification (OAS) v2.0, v3.0, or v3.1 definitions for target APIs
  • IDE with 42Crunch extension (VS Code, IntelliJ, or Eclipse)
  • CI/CD pipeline (Jenkins, GitHub Actions, Azure DevOps, or GitLab CI)
  • Running API instance for dynamic scanning (conformance scan)
  • Node.js or Python environment for CLI tooling

Core Concepts

API Audit (Static Analysis)

API Audit performs static security analysis of OpenAPI definitions without requiring a running API. It evaluates the specification against 300+ security checks organized into categories:

Security Score Categories:

  • Data Validation: Schema definitions, parameter constraints, response validation
  • Authentication: Security scheme definitions, scope requirements
  • Transport Security: Server URL schemes, TLS requirements
  • Error Handling: Error response definitions, information leakage prevention

Running API Audit via VS Code Extension:

  1. Install the 42Crunch extension from the VS Code marketplace
  2. Open an OpenAPI specification file (YAML or JSON)
  3. Click the security audit icon in the editor toolbar
  4. Review the security score (0-100) and individual findings
  5. Address issues using the inline remediation guidance

Example OpenAPI Definition with Security Controls:

yaml
openapi: 3.0.3
info:
  title: Secure User API
  version: 1.0.0
servers:
  - url: https://api.example.com/v1
    description: Production server (HTTPS only)
security:
  - BearerAuth: []
paths:
  /users/{userId}:
    get:
      operationId: getUserById
      summary: Retrieve user by ID
      parameters:
        - name: userId
          in: path
          required: true
          schema:
            type: string
            format: uuid
            pattern: '^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$'
            maxLength: 36
      responses:
        '200':
          description: User details
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/User'
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Unauthorized
        '404':
          description: User not found
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
  schemas:
    User:
      type: object
      required:
        - id
        - email
      properties:
        id:
          type: string
          format: uuid
          readOnly: true
        email:
          type: string
          format: email
          maxLength: 254
        name:
          type: string
          maxLength: 100
          pattern: '^[a-zA-Z\s\-]+$'
      additionalProperties: false
    Error:
      type: object
      required:
        - code
        - message
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
          maxLength: 256
      additionalProperties: false
API Conformance Scan (Dynamic Testing)

The conformance scan dynamically tests a running API against its OpenAPI contract to detect runtime vulnerabilities including OWASP API Security Top 10 issues:

Scan v2 Configuration:

yaml
# 42c-conf.yaml
version: "2.0"
scan:
  target:
    url: https://api.example.com/v1
  authentication:
    - type: bearer
      token: "${API_TOKEN}"
      in: header
      name: Authorization
  settings:
    maxScanTime: 3600
    requestsPerSecond: 10
    followRedirects: false
  tests:
    owasp:
      - bola
      - bfla
      - injection
      - ssrf
      - massAssignment
      - excessiveDataExposure

Running Conformance Scan via CLI:

bash
# Install the 42Crunch CLI
npm install -g @42crunch/cicd-cli

# Run conformance scan
42crunch-cli scan \
  --api-definition ./openapi.yaml \
  --target-url https://api.example.com/v1 \
  --token $CRUNCH_TOKEN \
  --min-score 70 \
  --report-format sarif \
  --output scan-report.sarif
CI/CD Pipeline Integration

GitHub Actions Integration:

yaml
name: API Security Testing
on:
  push:
    paths:
      - 'api/**'
      - 'openapi/**'
jobs:
  api-security:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: 42Crunch API Audit
        uses: 42Crunch/api-security-audit-action@v3
        with:
          api-token: ${{ secrets.CRUNCH_API_TOKEN }}
          collection-name: "my-api-collection"
          min-score: 75
          upload-to-code-scanning: true

      - name: 42Crunch Conformance Scan
        if: github.ref == 'refs/heads/main'
        uses: 42Crunch/api-conformance-scan@v1
        with:
          api-token: ${{ secrets.CRUNCH_API_TOKEN }}
          target-url: ${{ secrets.STAGING_API_URL }}
          scan-config: ./42c-conf.yaml

Jenkins Pipeline Integration:

groovy
pipeline {
    agent any
    stages {
        stage('API Security Audit') {
            steps {
                script {
                    def auditResult = sh(
                        script: '''
                            42crunch-cli audit \
                              --api-definition openapi.yaml \
                              --token ${CRUNCH_TOKEN} \
                              --min-score 75 \
                              --report-format json \
                              --output audit-report.json
                        ''',
                        returnStatus: true
                    )
                    if (auditResult != 0) {
                        error("API Security Audit failed - score below threshold")
                    }
                }
            }
        }
        stage('Conformance Scan') {
            when { branch 'main' }
            steps {
                sh '''
                    42crunch-cli scan \
                      --api-definition openapi.yaml \
                      --target-url ${STAGING_URL} \
                      --token ${CRUNCH_TOKEN} \
                      --scan-config 42c-conf.yaml
                '''
            }
        }
    }
    post {
        always {
            archiveArtifacts artifacts: '*-report.*'
            publishHTML([
                reportDir: '.',
                reportFiles: 'audit-report.html',
                reportName: 'API Security Report'
            ])
        }
    }
}
API Protect (Runtime Protection)

API Protect deploys as a micro-gateway in front of API endpoints to enforce the OpenAPI contract at runtime:

yaml
# api-protect-config.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: api-protect-config
data:
  protection-config.json: |
    {
      "apiDefinition": "/config/openapi.yaml",
      "enforcement": {
        "validateRequests": true,
        "validateResponses": true,
        "blockOnFailure": true,
        "logLevel": "warn"
      },
      "rateLimit": {
        "enabled": true,
        "requestsPerMinute": 100,
        "burstSize": 20
      },
      "allowlist": {
        "contentTypes": ["application/json"],
        "methods": ["GET", "POST", "PUT", "DELETE"]
      }
    }
Show full SKILL.md (222 more words)Show less

Remediation Workflow

When 42Crunch identifies issues, follow this remediation process:

  1. Triage: Review findings sorted by severity (Critical, High, Medium, Low)
  2. Analyze: Understand the specific security control missing from the OpenAPI definition
  3. Fix: Apply the recommended changes to the specification
  4. Validate: Re-run audit to confirm the score improvement
  5. Deploy: Push the updated specification through the CI/CD pipeline

Common Audit Findings and Fixes:

FindingSeverityFix
No authentication definedCriticalAdd securitySchemes and security requirements
Missing input validationHighAdd type, format, pattern, maxLength constraints
Server URL uses HTTPHighChange server URLs to HTTPS
No error responses definedMediumAdd 4xx and 5xx response definitions
additionalProperties not restrictedMediumSet additionalProperties: false on object schemas
Missing rate limitingMediumAdd x-rateLimit extension or use API Protect

Key Security Checks

42Crunch evaluates APIs against these critical security areas:

  • BOLA Prevention: Validates that object-level authorization patterns are defined
  • BFLA Prevention: Checks for function-level access control definitions
  • Injection Prevention: Ensures input parameters have proper type/format/pattern constraints
  • Data Exposure: Verifies response schemas limit returned properties
  • Security Misconfiguration: Checks authentication schemes, transport security, CORS settings
  • Mass Assignment: Validates that request bodies use explicit property allowlists

References

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/implementing-api-security-testing-with-42crunch of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • references/api-reference.md
  • scripts/agent.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Implementing API Security Testing With 42crunch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Implementing API Security Testing With 42crunch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implementing API Security Testing With 42crunch this skillmukul975/Anthropic-Cybersecurity-Skills34k—~2.8kAutomated safety check: PassApache-2.0
Mavenskjolber/3d-bin-container-packing568—~886Automated safety check: PassApache-2.0
API Security ReviewOWASP/secure-agent-playbook187—~744Automated safety check: PassCC-BY-4.0
Quarkus Verificationaffaan-m/ECC275k1 repos~2.7kAutomated safety check: PassMIT
Sast BanditAgentSecOps/SecOpsAgentKit2201 repos~2.6kAutomated safety check: PassCustom licence
Golang Securityunxed/f42412 repos~3.6kAutomated safety check: PassMIT

Similar skills

  • Maven

    skjolber/3d-bin-container-packing

    Maven build expertise for this multi-module Java project. An agent skill from skjolber/3d-bin-container-packing.

    568 GitHub stars~886 tokensUpdated today
    SecurityAuto-check passed
  • API Security Review

    OWASP/secure-agent-playbook

    Comprehensive API security review against OWASP API Security Top 10 (2023).

    187 GitHub stars~744 tokensUpdated 12 days ago
    SecurityAuto-check passed
  • Verification loop for Quarkus projects: build, static analysis (Checkstyle, PMD, SpotBugs), tests with JaCoCo coverage, OWASP dependency and container security scans, GraalVM native compilation…

    275k GitHub starsUsed in 1 repo~2.7k tokens
    SecurityAuto-check passed
  • Sast Bandit

    AgentSecOps/SecOpsAgentKit

    Python security vulnerability detection using Bandit SAST with CWE and OWASP mapping.

    220 GitHub starsUsed in 1 repo~2.6k tokens
    SecurityAuto-check passed
  • Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory…

    241 GitHub starsUsed in 2 repos~3.6k tokens
    SecurityAuto-check passed
  • Docs CI

    jh941213/my-cc-harness

    Scaffold a docs-as-code CI/CD pipeline + docs drift detection — link check, OpenAPI lint/breaking gate, mermaid validation, docs freshness check, CHANGELOG automation, docs.yaml manifest.

    126 GitHub stars~989 tokensUpdated 2 mo ago
    DevelopmentAuto-check: notes

More from mukul975/Anthropic-Cybersecurity-Skills

All 637 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Implementing API Security Testing With 42crunch

What does Implementing API Security Testing With 42crunch do?

Implements API security testing on the 42Crunch platform, combining API Audit for static analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability testing, and API Protect for…. Implementing API Security Testing With 42crunch is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Implements API security testing on the 42Crunch platform, combining API Audit for static analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability testing, and API Protect for runtime threat prevention, integrated into CI/CD pipelines and IDEs.

When should I use Implementing API Security Testing With 42crunch?

Implementing API Security Testing With 42crunch fits situations like: shift-left testing APIs for OWASP API Security Top 10 vulnerabilities; setting up 42Crunch audit and conformance scanning.

How do I install Implementing API Security Testing With 42crunch in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-api-security-testing-with-42crunch -a claude-code`. Or copy the skill folder (skills/implementing-api-security-testing-with-42crunch in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/implementing-api-security-testing-with-42crunch in your project. Claude Code loads it when a task matches its description.

How do I install Implementing API Security Testing With 42crunch in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-api-security-testing-with-42crunch -a codex`. Or copy the skill folder (skills/implementing-api-security-testing-with-42crunch in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/implementing-api-security-testing-with-42crunch in your project. Codex loads it when a task matches its description.

Can I use Implementing API Security Testing With 42crunch in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-api-security-testing-with-42crunch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementing-api-security-testing-with-42crunch, .gemini/skills/implementing-api-security-testing-with-42crunch, .github/skills/implementing-api-security-testing-with-42crunch and .opencode/skills/implementing-api-security-testing-with-42crunch in your project.

What does Implementing API Security Testing With 42crunch need to run?

Going by SKILL.md and its folder, Implementing API Security Testing With 42crunch needs Python for the scripts in its folder, the command-line tools its instructions call (npm) and credentials named CRUNCH_TOKEN, CRUNCH_API_TOKEN and API_TOKEN. Our summary lists: Python 3; Node.js; A credential in API_TOKEN; A credential in CRUNCH_TOKEN.

Does Implementing API Security Testing With 42crunch access the network?

SKILL.md names 5 domains. As links in the text: 42crunch.com, docs.42crunch.com, learn.microsoft.com, owasp.org and plugins.jenkins.io. This is read from the text; nothing was executed.

Is Implementing API Security Testing With 42crunch safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Implementing API Security Testing With 42crunch use?

Implementing API Security Testing With 42crunch is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implementing API Security Testing With 42crunch use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 388 tokens, read only when the agent opens those files.

What are the alternatives to Implementing API Security Testing With 42crunch?

Skills that share tags, products or a category with Implementing API Security Testing With 42crunch: Maven (skjolber/3d-bin-container-packing, 568 stars), API Security Review (OWASP/secure-agent-playbook, 187 stars), Quarkus Verification (affaan-m/ECC, 275k stars) and Sast Bandit (AgentSecOps/SecOpsAgentKit, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implementing API Security Testing With 42crunch?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 33,922 GitHub stars. The repository holds 637 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.