Borrowing it
Nothing to install: this file belongs to usk6666/yorishiro-proxy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/usk6666/yorishiro-proxy/main/.claude/skills/pentest-proxy/SKILL.mdgit clone --depth 1 https://github.com/usk6666/yorishiro-proxyWrote 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/usk6666/yorishiro-proxy/pentest-proxy)<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/pentest-proxy"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/pentest-proxy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/pentest-proxy"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/pentest-proxy.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.02712 |
| Opus 5.5 | $0.00007 | $0.01085 |
| Sonnet 5.5 | $0.00004 | $0.00542 |
| Haiku 4.5 | $0.00002 | $0.00271 |
Grade A, and why
pentest-proxy 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 8d 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.
Send requests through the proxy (e.g., curl, browser, or the target app) and list captured flows: How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pentest-proxy
Use yorishiro-proxy as an MITM proxy during penetration testing via CLI.
All commands use the yorishiro-proxy client subcommand over Bash.
Prerequisites
yorishiro-proxybinary is available on PATH- Target application is accessible from the proxy host
CLI Parameter Syntax
Parameters are key=value words; the CLI converts each value using the tool's input schema:
- Scalars are typed automatically (
limit=20is sent as an integer). - Arrays of scalars are comma-separated:
tls_passthrough.add='a.example.com,b.example.com'. - Dotted keys nest:
filter.outliers_only=true,params.flow_id=ID. Only the action-style tools (manage,security,intercept,macro,grpc_schema) take aparamsobject; typed tools such asresend_httpandfuzz_httptake their fields at the top level. - Objects and arrays of objects take JSON, quoted for the shell:
positions='[{"path":"raw_query","payloads":["a","b"]}]'. A'inside the single-quoted JSON is written'\''. key:=<json>sends any JSON value as-is (e.g.key:=null).
Run yorishiro-proxy client --help for the full grammar and yorishiro-proxy docs <tool> for each tool's parameters (no server needed).
1. Server Startup
Check if a server is already running:
yorishiro-proxy client list-servers
If no active server is found, start one:
yorishiro-proxy server -mcp-http-addr 127.0.0.1:9090 &
Verify it is ready:
yorishiro-proxy client query resource=status
2. Start Proxy Listener
yorishiro-proxy client proxy_start listen_addr=127.0.0.1:8080
Configure the target application or browser to use 127.0.0.1:8080 as its HTTP proxy.
3. Install CA Certificate
Export the CA certificate for HTTPS interception:
yorishiro-proxy client query resource=ca_cert
Install the output PEM into the target's trust store.
4. Configure TLS Passthrough (Optional)
Bypass TLS interception for specific upstream hosts (these hosts will NOT be intercepted):
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.
- 8d ago Changed · +35 lines d7fd603b2808
- 12d ago Changed · +2 lines e1ba5d93048a
- 1mo ago Changed · +1 lines 2b2f4f685413
- 1mo ago First seen · 222 lines · 18 tokens per session scan A e90d40ac7dbb
pentest-proxy is a skill published in the GitHub repository usk6666/yorishiro-proxy (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 2,712 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
screenshots
Advanced UI analysis and interaction through pixel-level reasoning to solve complex interaction problems, locate hard-to-find elements, verify visual states, and debug layout/rendering issues. Use as needed after UI Mapper inspection when advanced reasoning or non-standard views are required.
firmware-pentest
Firmware / IoT pentest chain. Start from a .bin / .img blob and close the full loop: reverse → extract → emulate → exploit. Methodology follows the OWASP FSTM nine stages; the toolchain centers on binwalk v3, unblob, EMBA, Firmadyne, and AFL++. Use cases: router/camera/smart-home firmware audits, firmware update…
ida-reverse
IDA Pro reverse engineering assistance skill. Be sure to use this skill whenever the user mentions reverse engineering, decompilation, analyzing binary/PE/ELF/APK/DLL/SO files, cracking, finding passwords, vulnerability analysis, malware analysis, or firmware analysis, or needs to analyze exe/dll/so/elf/macho/sys…
patch-diff-exploit
N-day patch diffing to exploitation. Reverse-engineer the vulnerability from vendor-released patches, write a PoC, and turn it into a usable attack module. Use cases: a known CVE with a patch but no PoC, SRC/red team targeting assets that have not been updated in time, N-day weaponization, Patch Tuesday follow-up.…
pentest-tools
Active penetration testing toolchain. Covers reconnaissance, port scanning, vulnerability scanning, web exploitation, SQL injection, directory brute-forcing, password cracking, and more. Exposes 20+ security tools to the AI agent via MCP servers (pentestMCP / mcp-security-hub). Trigger keywords: penetration testing…
reverse-engineering
Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it…