Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/marinahaugen/polymorph-mindset-plugins/pentestnpx skills add marinahaugen/polymorph-mindset-plugins --skill pentestgit clone --depth 1 https://github.com/marinahaugen/polymorph-mindset-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/marinahaugen/polymorph-mindset-plugins/pentest)<a href="https://agentmods.dev/skills/marinahaugen/polymorph-mindset-plugins/pentest"><img src="https://agentmods.dev/badge/skills/marinahaugen/polymorph-mindset-plugins/pentest.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00103 | $0.00890 |
| Opus 5 | $0.00051 | $0.00445 |
| Sonnet 5 | $0.00021 | $0.00178 |
| Haiku 4.5 | $0.00010 | $0.00089 |
Grade A, and why
pentest scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
5. **Security headers audit** (curl) — check for missing protective headers How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pentest Skill
Run structured penetration tests against web applications using the kali-pentest MCP server.
⚠️ Authorized use only. Run this only against systems you own or have explicit written permission to test. Unauthorized scanning is illegal in most jurisdictions.
Prerequisites Check
Before scanning, verify:
- Docker running:
docker pssucceeds - Kali image exists:
docker images kali-mcp-officialshows the image - MCP connected:
mcp__kali-pentest__server_healthtool is available and returns healthy
If any prerequisite fails, guide the user:
- No Docker:
open -a Docker(macOS) - No image: build from
.pentest/Dockerfilein project root - No MCP: ensure
.mcp.jsonexists in project root with kali-pentest config, restart session
Target Selection
Ask the user which target to scan:
- Local dev (
localhost:3000): Usehost.docker.internalas the target hostname (macOS Docker cannot reach host localhost directly) - Staging/Production (e.g.
staging.example.com): Use the hostname directly
Scan Sequence
Use mcp__kali-pentest__execute_command for ALL scans (the dedicated API wrapper tools like nmap_scan return 500 errors — always use execute_command with CLI commands directly).
Run scans in this order. See references/scans.md for exact commands.
Phase 1: Reconnaissance
- Port scan (nmap) — discover open ports and services
- Version detection (nmap) — identify software versions on interesting ports
Phase 2: Vulnerability Scanning
- Web server scan (nikto) — common web vulnerabilities, misconfigs
- Directory discovery (dirb) — hidden endpoints, admin panels, API routes
- Security headers audit (curl) — check for missing protective headers
- Sensitive files check (curl) —
.env,.git/config,robots.txt, etc.
Phase 3: Auth & Access Testing
- Auth bypass tests — CVE-2025-29927 middleware bypass header, unauthenticated API access
- Cookie security check — HttpOnly, Secure, SameSite flags
- TLS configuration — verify TLS 1.0/1.1 rejected, check cipher strength
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 77 lines · 103 tokens per session scan A 7cd7056a3c62
pentest is a skill published in the GitHub repository marinahaugen/polymorph-mindset-plugins (4 stars, last pushed 2mo ago), licensed MIT. It adds 103 tokens to every session and 890 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…