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/greglas75/zuvo/pentestnpx skills add greglas75/zuvo --skill pentestgit clone --depth 1 https://github.com/greglas75/zuvoWrote 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/greglas75/zuvo/pentest)<a href="https://agentmods.dev/skills/greglas75/zuvo/pentest"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/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.00124 | $0.10406 |
| Opus 5 | $0.00062 | $0.05203 |
| Sonnet 5 | $0.00025 | $0.02081 |
| Haiku 4.5 | $0.00012 | $0.01041 |
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 3d 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.
which curl 2>/dev/null && echo "curl: OK" || echo "curl: MISSING" How it starts
The opening of the file, as written. The whole thing — 888 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:pentest -- Hybrid Penetration Testing
White-box source-to-sink analysis combined with optional black-box runtime verification. zuvo:pentest is stack-aware: it selects sources, sinks, framework-safe patterns, and CodeSift recipes based on the detected project stack before dispatching any agents. Findings are built from a deterministic candidate schema, then merged with canonical-key deduplication and centralized scoring.
When to use: Before releases, after zuvo:security-audit flags issues that need exploit verification, testing CMS installations, verifying security fixes.
Out of scope: Static code quality (use zuvo:code-audit), broad security posture review (use zuvo:security-audit), API contract audit (use zuvo:api-audit).
Argument Parsing
| Argument | Effect |
|---|---|
[path] |
Limit analysis to a specific directory |
--url <url> |
Target URL for runtime probes (enables hybrid mode) |
--from-audit <dir> |
VERIFICATION mode -- verify PT/SEC findings from a prior audit directory |
--cms joomla|wordpress|drupal |
Force-enable CMS overlay |
--quick |
PT1 + PT3 + PT4 only (critical gates), no live probing |
--scope <path> |
Alias for [path] |
--dimensions PT1,PT2 |
Audit only specified dimensions |
--verify-live |
Enable Phase 3 exploit verification against a running app |
--rate <N> |
Requests per second cap (default: 5) |
--source |
Force white-box track only -- skip live probes even if --url present |
--runtime |
Force black-box track only -- skip source analysis. Requires --url. |
--strict-v2 |
Count the 14 v2 vuln classes toward score caps / critical-gate totals — the 11 original (incl. both GraphQL classes) plus header_injection, token_compare_bypass, weak_credential_storage added 2026-08-01. Default: warning-only grace — identical spec to security-audit's "v2 class grace" section, and the graced set is all 14, not the original 11: a class added to v2 is a v2 class, and gracing 11 of 14 would silently enforce the three newest on day one. Warning-only through the 1.4.x window, full weight in 1.5.0; v2 findings are still reported + backlogged, excluded only from gate totals; identical v2-grace: warning-only (N v2 findings reported + backlogged, excluded from gate; --strict-v2 to enforce) line. |
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.
- 3d ago First seen · 888 lines · 124 tokens per session scan A f1a51eeee6f1
pentest is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed today), licensed MIT. It adds 124 tokens to every session and 10,406 once invoked, about $0.0006 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
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…
ring:checking-frontend-quality
Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…
ring:creating-helm-charts
Creating Helm charts to Lerian conventions via ring:helm: standardized chart structure, full env-var coverage from .env.example, security defaults (runAsNonRoot, readOnlyRootFilesystem), ClusterIP-only services, and health probes; validates helm lint and template render. Use when creating, modifying, or reviewing a…