penetration-test-planner
Plan penetration test planner operations. Auto-activating skill for Security Advanced. Triggers on: penetration test planner, penetration test planner Part of the Security Advanced skill category. Use when writing or running tests. Trigger with phrases like "penetration test planner", "penetration planner", "penetration". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill penetration-test-planner --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Penetration Test Planner ## Overview This skill provides automated assistance for penetration test planner tasks within the Security Advanced domain. ## When to Use This skill activates automatically when you: - Mention "penetration test planner" in your request - Ask about penetration test planner patterns or best practices - Need help with advanced security skills covering penetration testing,
What does the penetration-test-planner skill do?
Plan penetration test planner operations. Auto-activating skill for Security Advanced. Triggers on: penetration test planner, penetration test planner Part of the Security Advanced skill category. Use when writing or running tests. Trigger with phrases like "penetration test planner", "penetration planner", "penetration". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill penetration-test-planner --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.