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.
Plan an authorized PCI DSS penetration test around the cardholder data environment, critical systems, internal and external coverage, segmentation, tester independence, remediation, retesting, and…
Install Plan Pci Dss Penetration Test
$ npx skills add cyberful/cyberful --skill plan-pci-dss-penetration-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cyberful/cyberful plan-pci-dss-penetration-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/plan-pci-dss-penetration-test .claude/skills/plan-pci-dss-penetration-test && rm -rf skills-srcUse ~/.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/
Install the "plan-pci-dss-penetration-test" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/plan-pci-dss-penetration-test into .claude/skills/plan-pci-dss-penetration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-pci-dss-penetration-test", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/plan-pci-dss-penetration-testType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cyberful/cyberful --skill plan-pci-dss-penetration-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cyberful/cyberful plan-pci-dss-penetration-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cyberful/builtin/skills/plan-pci-dss-penetration-test .agents/skills/plan-pci-dss-penetration-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-pci-dss-penetration-test" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/plan-pci-dss-penetration-test into .agents/skills/plan-pci-dss-penetration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-pci-dss-penetration-test", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cyberful/cyberful --skill plan-pci-dss-penetration-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cyberful/cyberful plan-pci-dss-penetration-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cyberful/builtin/skills/plan-pci-dss-penetration-test .cursor/skills/plan-pci-dss-penetration-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-pci-dss-penetration-test" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/plan-pci-dss-penetration-test into .cursor/skills/plan-pci-dss-penetration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-pci-dss-penetration-test", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cyberful/cyberful.git --path cyberful/builtin/skills/plan-pci-dss-penetration-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cyberful/cyberful --skill plan-pci-dss-penetration-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cyberful/cyberful plan-pci-dss-penetration-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cyberful/builtin/skills/plan-pci-dss-penetration-test .gemini/skills/plan-pci-dss-penetration-test && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-pci-dss-penetration-test" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/plan-pci-dss-penetration-test into .gemini/skills/plan-pci-dss-penetration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-pci-dss-penetration-test", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cyberful/cyberful plan-pci-dss-penetration-testInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cyberful/cyberful --skill plan-pci-dss-penetration-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .github/skills && cp -r skills-src/cyberful/builtin/skills/plan-pci-dss-penetration-test .github/skills/plan-pci-dss-penetration-test && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-pci-dss-penetration-test" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/plan-pci-dss-penetration-test into .github/skills/plan-pci-dss-penetration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-pci-dss-penetration-test", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cyberful/cyberful --skill plan-pci-dss-penetration-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cyberful/cyberful plan-pci-dss-penetration-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cyberful/builtin/skills/plan-pci-dss-penetration-test .opencode/skills/plan-pci-dss-penetration-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-pci-dss-penetration-test" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/plan-pci-dss-penetration-test into .opencode/skills/plan-pci-dss-penetration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-pci-dss-penetration-test", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan-pci-dss-penetration-test- GitHub stars
- 135
- Token cost
- ~943 tokens
- SKILL.md length
- 328 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 85
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Plan an authorized PCI DSS penetration test around the cardholder data environment, critical systems, internal and external coverage, segmentation, tester independence, remediation, retesting, and…
- Defining a PCI DSS 11.4 methodology
- SKILL.md covers Establish the planning basis, Resolve scope before coverage, Produce the engagement contract and Close planning gaps explicitly, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Healthcare and finance regulation
What it does
Plan Pci Dss Penetration Test is an agent skill from cyberful/cyberful. Plan an authorized PCI DSS penetration test around the cardholder data environment, critical systems, internal and external coverage, segmentation, tester independence, remediation, retesting, and evidence retention. Use when defining a PCI DSS 11.4 methodology or engagement.
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `agents/openai.yaml`, `assets/pci-penetration-test-plan.schema.json` and `assets/pci-penetration-test-plan.template.json`).
It sits in Legal & Compliance, covering Healthcare and finance regulation. 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
- Defining a PCI DSS 11.4 methodology
- Tasks that involve Healthcare and finance regulation
Example prompts
- “/plan-pci-dss-penetration-test”
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
No scripts in the folder and no shell commands in SKILL.md.
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.orgpcisecuritystandards.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
Plan Pci Dss Penetration Test loads about 943 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 77 tokens; SKILL.md has 328 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 328 words, ~943 tokens.
Download SKILL.mdSave it as
.claude/skills/plan-pci-dss-penetration-test/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- plan-pci-dss-penetration-test
- description
- Plan an authorized PCI DSS penetration test around the cardholder data environment, critical systems, internal and external coverage, segmentation, tester independence, remediation, retesting, and evidence retention. Use when defining a PCI DSS 11.4 methodology or engagement.
- metadata.domain
- payment-security
- metadata.subdomain
- pci-penetration-planning
- metadata.triggers
- pci dss penetration test plan, pci dss 11.4 methodology, cardholder environment pen test planning, internal external pci penetration testing, pci test rules…
- metadata.tags
- pci-dss, requirement-11.4, cde, penetration-testing, rules-of-engagement, retest
Plan a PCI DSS Penetration Test
Build a test plan that is authorized, representative of the real cardholder data environment, and traceable to the entity's defined methodology. Do not treat a vulnerability scan, an ASV scan, or a generic application test as a substitute for penetration testing.
Establish the planning basis
Read references/pci-penetration-methodology.md. Treat PCI DSS v4.0.1 as normative. Use the PCI SSC Penetration Testing Guidance v1.1 only as supplemental methodology: it predates v4.0.1 and references the former Requirement 11.3.
Confirm the entity type, assessment period, authorization owner, tester independence, CDE owner, significant changes, previous threats and vulnerabilities, and evidence-handling restrictions. A plan records authority; it does not create it.
Resolve scope before coverage
Use trace-cardholder-data-environment when CDE boundaries, account-data flows, connected-to systems, critical systems, third-party paths, administrative access, or scope-reduction claims are uncertain. Do not silently accept a supplied asset list as the complete CDE.
Define internal and external vantage points and both application-layer and network-layer coverage. Relate every target and test family to a CDE boundary, critical system, data flow, scope-reduction control, significant change, or threat observed during the previous 12 months.
Use test-cardholder-data-segmentation when segmentation reduces scope. Cover every segmentation method in use and record why any representative sampling is sufficient.
Produce the engagement contract
Complete assets/pci-penetration-test-plan.template.json under assets/pci-penetration-test-plan.schema.json. Include rules of engagement, stop conditions, communication and incident paths, handling of encountered account data, tester-origin details, test windows, request or effect limits, cleanup, success criteria, evidence retention, remediation ownership, and retest criteria.
Route specialist execution to the narrowest Cyberful skills. Preserve the plan as the coverage ledger that ties their evidence together; do not duplicate their procedures here.
Close planning gaps explicitly
Do not label an unknown boundary, unavailable environment, absent test account, or unapproved effect as covered. Record the exact dependency and owner. After execution, use audit-pci-dss-penetration-test-evidence to reconcile the plan, results, remediation, and retests without issuing an automated compliance verdict.
Authoritative anchors
- PCI DSS v4.0.1: https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0_1.pdf
- PCI SSC Penetration Testing Guidance v1.1: https://www.pcisecuritystandards.org/documents/Penetration-Testing-Guidance-v1_1.pdf
© 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 4 other files (references, assets) in cyberful/builtin/skills/plan-pci-dss-penetration-test of cyberful/cyberful.
- SKILL.md
- agents/openai.yaml
- assets/pci-penetration-test-plan.schema.json
- assets/pci-penetration-test-plan.template.json
- references/pci-penetration-methodology.md
Open the folder on GitHubat commit ec598a6
Compare with similar skills
Plan Pci Dss Penetration Test 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan Pci Dss Penetration Test this skillcyberful/cyberful | 135 | — | ~943 | Automated safety check: Pass | AGPL-3.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed | 5.5k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~4.6k | Automated safety check: Notes | MIT | |
| Fda Consultant Specialistdavila7/claude-code-templates | 33k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
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.
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
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.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Grc Knowledge
mlunato47/claude-grc-plugin
Senior GRC analyst expertise across 18 compliance frameworks — NIST 800-53, FedRAMP (Rev5 + 20x/CR26, KSIs, VDR/VER, Certification Classes A–D), DoD/DoW Impact Levels (IL2–IL6, DISA Cloud SRG), ITAR…
More from cyberful/cyberful
All 85 skills in this repoAudit Infrastructure As Code
cyberful/cyberful
Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.
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.
Audit Pci Dss Penetration Test Evidence
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.
Operate Content Discovery
cyberful/cyberful
Design and interpret advanced content discovery with ffuf and complementary web fuzzers.
Operate Network Recon
cyberful/cyberful
Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.
Operate Sast Toolchain
cyberful/cyberful
Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.
Related
Categories
Questions about Plan Pci Dss Penetration Test
What does Plan Pci Dss Penetration Test do?
Plan an authorized PCI DSS penetration test around the cardholder data environment, critical systems, internal and external coverage, segmentation, tester independence, remediation, retesting, and…. Plan Pci Dss Penetration Test is an agent skill from cyberful/cyberful. Plan an authorized PCI DSS penetration test around the cardholder data environment, critical systems, internal and external coverage, segmentation, tester independence, remediation, retesting, and evidence retention.
When should I use Plan Pci Dss Penetration Test?
Plan Pci Dss Penetration Test fits situations like: defining a PCI DSS 11.4 methodology; tasks that involve Healthcare and finance regulation.
How do I install Plan Pci Dss Penetration Test in Claude Code?
Run `npx skills add cyberful/cyberful --skill plan-pci-dss-penetration-test -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/plan-pci-dss-penetration-test in cyberful/cyberful) into .claude/skills/plan-pci-dss-penetration-test in your project. Claude Code loads it when a task matches its description.
How do I install Plan Pci Dss Penetration Test in Codex?
Run `npx skills add cyberful/cyberful --skill plan-pci-dss-penetration-test -a codex`. Or copy the skill folder (cyberful/builtin/skills/plan-pci-dss-penetration-test in cyberful/cyberful) into .agents/skills/plan-pci-dss-penetration-test in your project. Codex loads it when a task matches its description.
Can I use Plan Pci Dss Penetration Test 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 plan-pci-dss-penetration-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-pci-dss-penetration-test, .gemini/skills/plan-pci-dss-penetration-test, .github/skills/plan-pci-dss-penetration-test and .opencode/skills/plan-pci-dss-penetration-test in your project.
What does Plan Pci Dss Penetration Test need to run?
SKILL.md names no scripts, command-line tools or credentials: Plan Pci Dss Penetration Test is instructions for the agent only.
Does Plan Pci Dss Penetration Test 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 Plan Pci Dss Penetration Test 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. Review the folder before installing.
What licence does Plan Pci Dss Penetration Test use?
Plan Pci Dss Penetration Test 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 Plan Pci Dss Penetration Test use?
About 943 tokens (SKILL.md is roughly 3.8k 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 793 tokens, read only when the agent opens those files.
What are the alternatives to Plan Pci Dss Penetration Test?
Skills that share tags, products or a category with Plan Pci Dss Penetration Test: 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 Plan Pci Dss Penetration Test?
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.