Back to catalog
Static reviewDevelopment

Skill dossier

implementing-fuzz-testing-in-cicd-with-aflplusplus

Source declaration

Integrates AFL++ coverage-guided fuzzing into CI/CD pipelines, covering harness construction, AFL++/AddressSanitizer/CmpLog instrumentation builds, and persistent-mode fuzzing to discover memory-corruption and input-handling vulnerabilities in C/C++ code. Use when adding automated fuzz testing to a build pipeline or hunting for memory-safety bugs in native/compiled applications.

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

Integrates AFL++ coverage-guided fuzzing into CI/CD pipelines, covering harness construction, AFL++/AddressSanitizer/CmpLog instrumentation builds, and persistent-mode fuzzing to discover memory-corruption and input-handling vulnerabilities in C/C++ code. Use when adding automated fuzz testing to a build pipeline or hunting for memory-safety bugs in native/compiled applications.

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 AFL++ coverage-guided fuzzing into CI/CD pipelines, covering harness construction, AFL++/AddressSanitizer/CmpLog instrumentation builds, and persistent-mode fuzzing to discover memory-corruption and input-handling vulnerabilities in C/C++ code. Use when adding automated fuzz testing to a build pipeline or hunting for memory-safety bugs in native/compiled applications. 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/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.md:L99]
  • Step 1 --- Build the Fuzzing Harness [Source statement; provisional, not tested. Evidence: skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.md:L101]
  • Step 2 --- Compile with AFL++ Instrumentation [Source statement; provisional, not tested. Evidence: skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.md:L132]
  • Step 3 --- Prepare Seed Corpus [Source statement; provisional, not tested. Evidence: skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.md:L150]
  • Step 4 --- Configure CI/CD Integration [Source statement; provisional, not tested. Evidence: skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.md:L165]
  • Step 5 --- Parallel Fuzzing for Nightly Runs [Source statement; provisional, not tested. Evidence: skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.md:L234]
  • Step 6 --- Crash Triage [Source statement; provisional, not tested. Evidence: skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.md:L252]

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/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.md:L1-L36]

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
38 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/assets/template.mdReference893 B
skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/LICENSEOther11 KB
skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/references/api-reference.mdReference2.1 KB
skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/references/standards.mdReference1.8 KB
skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/references/workflows.mdReference1.4 KB
skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/scripts/agent.pyScript6.8 KB
skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/scripts/process.pyScript5.9 KB
skills/implementing-fuzz-testing-in-cicd-with-aflplusplus/SKILL.mdInstruction8.3 KB

SKILL.md frontmatter

{
  "name": "implementing-fuzz-testing-in-cicd-with-aflplusplus",
  "description": "Integrates AFL++ coverage-guided fuzzing into CI/CD pipelines, covering harness construction, AFL++/AddressSanitizer/CmpLog instrumentation builds, and persistent-mode fuzzing to discover memory-corruption and input-handling vulnerabilities in C/C++ code. Use when adding automated fuzz testing to a build pipeline or hunting for memory-safety bugs in native/compiled applications.",
  "domain": "cybersecurity",
  "subdomain": "devsecops",
  "tags": [
    "aflplusplus",
    "fuzz-testing",
    "cicd",
    "coverage-guided-fuzzing",
    "security-testing",
    "vulnerability-discovery",
    "afl"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_ai_rmf": [
    "MEASURE-2.7",
    "MAP-5.1",
    "MANAGE-2.4"
  ],
  "atlas_techniques": [
    "AML.T0070",
    "AML.T0066",
    "AML.T0082"
  ],
  "nist_csf": [
    "PR.PS-01",
    "GV.SC-07",
    "ID.IM-04",
    "PR.PS-04"
  ],
  "mitre_attack": [
    "T1195",
    "T1554",
    "T1059.004",
    "T1005",
    "T1059"
  ]
}

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
    Action

    Overview

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

  2. 02
    Decision

    When to Use

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

  3. 03
    Action

    Core Concepts

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

  4. 04
    Action

    Workflow

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

  5. 05
    Action

    Step 1 --- Build the Fuzzing Harness

    Source-described action candidate under “Step 1 --- Build the Fuzzing Harness”; not verified execution.

  6. 06
    Input

    Create a harness that feeds AFL++ input to the target function:

    Source-described input candidate under “Step 1 --- Build the Fuzzing Harness”; not verified execution.

Inspect all extracted workflow candidates (14 candidate steps)
  1. 07
    Action

    Step 2 --- Compile with AFL++ Instrumentation

    Source-described action candidate under “Step 2 --- Compile with AFL++ Instrumentation”; not verified execution.

  2. 08
    Action

    Step 3 --- Prepare Seed Corpus

    Source-described action candidate under “Step 3 --- Prepare Seed Corpus”; not verified execution.

  3. 09
    Action

    Step 4 --- Configure CI/CD Integration

    Source-described action candidate under “Step 4 --- Configure CI/CD Integration”; not verified execution.

  4. 10
    Action

    Step 5 --- Parallel Fuzzing for Nightly Runs

    Source-described action candidate under “Step 5 --- Parallel Fuzzing for Nightly Runs”; not verified execution.

  5. 11
    Action

    Step 6 --- Crash Triage

    Source-described action candidate under “Step 6 --- Crash Triage”; not verified execution.

  6. 12
    Action

    CI/CD Best Practices for AFL++

    Source-described action candidate under “CI/CD Best Practices for AFL++”; not verified execution.

  7. 13
    Action

    Monitoring Fuzzing Campaigns

    Source-described action candidate under “Monitoring Fuzzing Campaigns”; not verified execution.

  8. 14
    Action

    References

    Source-described action candidate under “References”; 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.

Attention recommended

36 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

7 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 7 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

27 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 27 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

2 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 2 location(s) in the collected text; 2 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/implementing-fuzz-testing-in-cicd-with-aflplusplus/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/implementing-fuzz-testing-in-cicd-with-aflplusplus/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/implementing-fuzz-testing-in-cicd-with-aflplusplus
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.