New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Audit Pci Dss Penetration Test Evidence

by cyberful in cyberful/cyberful

Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.

AGPL-3.0Auto-check passedLegal & Compliance

Install Audit Pci Dss Penetration Test Evidence

skills CLI
$ npx skills add cyberful/cyberful --skill audit-pci-dss-penetration-test-evidence -a claude-code

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

GitHub CLI
$ gh skill install cyberful/cyberful audit-pci-dss-penetration-test-evidence --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/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/audit-pci-dss-penetration-test-evidence .claude/skills/audit-pci-dss-penetration-test-evidence && 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
audit-pci-dss-penetration-test-evidence
GitHub stars
135
Token cost
~1k tokens
SKILL.md length
327 words
Files
9 (incl. scripts, references, assets)
Skills in repo
85
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.

  • Identify unsupported Requirement 11.4 coverage without issuing a compliance verdict
  • SKILL.md covers Establish applicability, Reconcile the evidence chain, Normalize bounded evidence… and Conclude at the evidence…, plus 1 more section
  • Runs Python scripts from its folder
  • Tasks that involve Healthcare and finance regulation

What it does

Audit Pci Dss Penetration Test Evidence is an agent skill from cyberful/cyberful. Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence. Use to identify unsupported Requirement 11.4 coverage without issuing a compliance verdict.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts, reference files and assets (for example `agents/openai.yaml`, `assets/pci-penetration-evidence-audit.schema.json` and `assets/pci-penetration-evidence.example.json`).

It sits in Legal & Compliance, covering Healthcare and finance regulation and Multi-tenancy. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.

When your agent uses it

  • Identify unsupported Requirement 11.4 coverage without issuing a compliance verdict
  • Tasks that involve Healthcare and finance regulation
  • Tasks that involve Multi-tenancy

Example prompts

  • “/audit-pci-dss-penetration-test-evidence”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit ec598a6. 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 2 files in scripts/ (Python), which the agent can run.

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

    • docs-prv.pcisecuritystandards.org
    • pcisecuritystandards.org

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Audit Pci Dss Penetration Test Evidence loads about 1k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 327 words of instructions outside code blocks.

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

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 cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 327 words, ~1,023 tokens.

Download SKILL.mdSave it as .claude/skills/audit-pci-dss-penetration-test-evidence/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
audit-pci-dss-penetration-test-evidence
description
Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence. Use to identify unsupported Requirement 11.4 coverage without issuing a compliance verdict.
metadata.domain
payment-security
metadata.subdomain
pci-penetration-evidence
metadata.triggers
audit pci dss penetration test evidence, review pci dss 11.4 report, pci penetration test evidence gap, validate pci retest documentation, review pci…
metadata.tags
pci-dss, requirement-11.4, evidence-review, penetration-test-report, remediation, retest

Audit PCI DSS Penetration-Test Evidence

Audit whether the evidence set supports the entity's documented Requirement 11.4 claims. Review evidence identity, period, scope, provenance, applicability, and consistency; do not convert document presence into a PCI DSS compliance conclusion.

Establish applicability

Read references/evidence-evaluation-method.md. Confirm PCI DSS version, entity type, whether segmentation reduces scope, assessment period, significant changes, validation process, and the evidence owner. Requirements 11.4.6 and 11.4.7 have service-provider applicability that must not be inferred from a report title.

Reconcile the evidence chain

Compare the defined methodology, current CDE trace, scope of work, internal and external reports, test dates, change-triggered tests, tester qualifications and independence, segmentation coverage, finding risk treatment, remediation records, repeated tests, retention, and customer-support evidence where applicable.

For every claim, preserve the exact evidence reference and the element it supports. Distinguish absent evidence, stale evidence, inconsistent scope, unresolved applicability, unsupported sampling, missing remediation, and missing retest. Do not accept a clean executive summary as proof that the required attack surfaces and methods were exercised.

Normalize bounded evidence metadata

Use scripts/audit_pci_penetration_evidence.py only on a staged metadata ledger that contains no PAN, SAD, credentials, report bodies, or other payment secrets. Start from assets/pci-penetration-evidence.example.json and retain assets/pci-penetration-evidence.schema.json.

The offline analyzer groups exact evidence references, derives the requirement set implied by entity type and segmentation use, and reports unobserved requirements, requirements without supported evidence metadata, same-topic status conflicts, and applicability warnings. Its output follows assets/pci-penetration-evidence-audit.schema.json. It does not read referenced evidence, judge tester competence, validate a technical finding, or decide compliance.

Conclude at the evidence boundary

Report what is supported, what is missing, what conflicts, what is blocked, and the shortest next discriminator. Route scope contradictions to trace-cardholder-data-environment, methodology gaps to plan-pci-dss-penetration-test, and isolation claims to test-cardholder-data-segmentation.

Do not create an AOC, ROC, SAQ response, QSA opinion, or certification statement. Formal applicability and compliance decisions remain with the entity, its assessor where applicable, and the compliance-accepting entity.

Authoritative anchors

© cyberful, AGPL-3.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 8 other files (scripts, references, assets) in cyberful/builtin/skills/audit-pci-dss-penetration-test-evidence of cyberful/cyberful.

  • SKILL.md
  • agents/openai.yaml
  • assets/pci-penetration-evidence-audit.schema.json
  • assets/pci-penetration-evidence.example.json
  • assets/pci-penetration-evidence.schema.json
  • references/evidence-evaluation-method.md
  • scripts/audit_pci_penetration_evidence.py
  • scripts/manifest.json
  • tests/test_audit_pci_penetration_evidence.py

Open the folder on GitHubat commit ec598a6

Compare with similar skills

Audit Pci Dss Penetration Test Evidence 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.

Audit Pci Dss Penetration Test Evidence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Pci Dss Penetration Test Evidence this skillcyberful/cyberful135—~1kAutomated safety check: PassAGPL-3.0
HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed5.5k—~1.7kAutomated safety check: PassApache-2.0
HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed5.5k—~2kAutomated safety check: PassApache-2.0
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~2.3kAutomated safety check: PassMIT
ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills48k1 repos~4.6kAutomated safety check: NotesMIT
Fda Consultant Specialistdavila7/claude-code-templates33k1 repos~2.7kAutomated safety check: PassMIT

Similar skills

  • HIPAA Safe Harbor Coverage Audit

    maziyarpanahi/openmed

    Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.

    5.5k GitHub stars~1.7k tokensUpdated today
    Legal & ComplianceAuto-check passed

  • HIPAA Pre-Deployment Compliance Check

    maziyarpanahi/openmed

    Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.

    5.5k GitHub stars~2k tokensUpdated today
    Legal & ComplianceAuto-check passed

  • Hipaa Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert HIPAA compliance assistant for healthcare and software contexts.

    946 GitHub starsUsed in 1 repo~2.3k tokens
    Legal & ComplianceAuto-check passed

  • ISO Standards Readiness Evidence

    K-Dense-AI/scientific-agent-skills

    Organizes scope, controlled documents, risk files and traceability into draft evidence for human review against ISO 13485, 14971, 17025 and 15189.

    48k GitHub starsUsed in 1 repo~4.6k tokens
    Legal & ComplianceAuto-check: notes

  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    33k GitHub starsUsed in 1 repo~2.7k tokens
    Legal & ComplianceAuto-check passed

  • Eks Best Practices

    aws-samples/appmod-blueprints

    Official

    Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning.

    115 GitHub stars~5k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

More from cyberful/cyberful

All 85 skills in this repo

  • Audit Infrastructure As Code

    cyberful/cyberful

    Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.

    135 GitHub stars~649 tokensUpdated 1 mo ago
    Auto-check passed

  • Audit Kubernetes Policy Enforcement

    cyberful/cyberful

    Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.

    135 GitHub stars~610 tokensUpdated 1 mo ago
    Auto-check passed

  • Operate Content Discovery

    cyberful/cyberful

    Design and interpret advanced content discovery with ffuf and complementary web fuzzers.

    135 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Operate Network Recon

    cyberful/cyberful

    Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.

    135 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Operate Sast Toolchain

    cyberful/cyberful

    Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.

    135 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Operate Supply Chain Toolchain

    cyberful/cyberful

    Operate Syft, Grype, Trivy, Gitleaks, Retire.js, package-manager metadata, and build evidence for advanced software-supply-chain assessment.

    135 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Audit Pci Dss Penetration Test Evidence

What does Audit Pci Dss Penetration Test Evidence do?

Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence. Audit Pci Dss Penetration Test Evidence is an agent skill from cyberful/cyberful. Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.

When should I use Audit Pci Dss Penetration Test Evidence?

Audit Pci Dss Penetration Test Evidence fits situations like: identify unsupported Requirement 11.4 coverage without issuing a compliance verdict; tasks that involve Healthcare and finance regulation; tasks that involve Multi-tenancy.

How do I install Audit Pci Dss Penetration Test Evidence in Claude Code?

Run `npx skills add cyberful/cyberful --skill audit-pci-dss-penetration-test-evidence -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/audit-pci-dss-penetration-test-evidence in cyberful/cyberful) into .claude/skills/audit-pci-dss-penetration-test-evidence in your project. Claude Code loads it when a task matches its description.

How do I install Audit Pci Dss Penetration Test Evidence in Codex?

Run `npx skills add cyberful/cyberful --skill audit-pci-dss-penetration-test-evidence -a codex`. Or copy the skill folder (cyberful/builtin/skills/audit-pci-dss-penetration-test-evidence in cyberful/cyberful) into .agents/skills/audit-pci-dss-penetration-test-evidence in your project. Codex loads it when a task matches its description.

Can I use Audit Pci Dss Penetration Test Evidence 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 cyberful/cyberful --skill audit-pci-dss-penetration-test-evidence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-pci-dss-penetration-test-evidence, .gemini/skills/audit-pci-dss-penetration-test-evidence, .github/skills/audit-pci-dss-penetration-test-evidence and .opencode/skills/audit-pci-dss-penetration-test-evidence in your project.

What does Audit Pci Dss Penetration Test Evidence need to run?

Going by SKILL.md and its folder, Audit Pci Dss Penetration Test Evidence needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Audit Pci Dss Penetration Test Evidence access the network?

SKILL.md names 2 domains. As links in the text: docs-prv.pcisecuritystandards.org and pcisecuritystandards.org. This is read from the text; nothing was executed.

Is Audit Pci Dss Penetration Test Evidence 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 Audit Pci Dss Penetration Test Evidence use?

Audit Pci Dss Penetration Test Evidence is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audit Pci Dss Penetration Test Evidence use?

About 1k tokens (SKILL.md is roughly 4.1k 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 674 tokens, read only when the agent opens those files.

What are the alternatives to Audit Pci Dss Penetration Test Evidence?

Skills that share tags, products or a category with Audit Pci Dss Penetration Test Evidence: HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars) and ISO Standards Readiness Evidence (K-Dense-AI/scientific-agent-skills, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Pci Dss Penetration Test Evidence?

cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 135 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.

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