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.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.1 | $0.00018 | $0.01739 |
| Opus 5 | $0.00009 | $0.00870 |
| Sonnet 5 | $0.00004 | $0.00348 |
| Haiku 4.5 | $0.00002 | $0.00174 |
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 — 222 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
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):
yorishiro-proxy client configure tls_passthrough.add='*.cdn.example.com,static.example.com'
5. Capture Traffic
Send requests through the proxy (e.g., curl, browser, or the target app) and list captured flows:
yorishiro-proxy client query resource=flows limit=20
6. Inspect a Flow
yorishiro-proxy client query flow FLOW_ID
yorishiro-proxy client query messages FLOW_ID
Note:
querysupports positional args: first arg isresource, second isid.
7. Resend a Request
Replay a recorded request as-is:
yorishiro-proxy client resend action=resend params.flow_id=FLOW_ID
Compare the original and replayed responses:
yorishiro-proxy client resend action=compare params.flow_id_a=ORIGINAL_ID params.flow_id_b=REPLAYED_ID
8. Fuzz a Parameter
Launch a fuzz campaign against a captured flow. The fuzz tool requires structured JSON for positions and payload sets, so use @- (stdin) or a JSON file for complex configurations:
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 First seen · 222 lines · 18 tokens per session scan A e90d40ac7dbb
pentest-proxy is a skill published in the GitHub repository usk6666/yorishiro-proxy (16 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 1,739 once invoked, about $0.0001 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-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.
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…
ReverseOps-router
Routes reverse engineering, exploitation, penetration testing, malware, mobile, firmware, browser automation, documentation, and security tasks to the appropriate specialist skill. Use when a task spans modules or the correct ReverseOps entrypoint is unclear.
apk-reverse
Use when performing Android APK reverse engineering in a CLI environment. Applies to APK unpacking, Java decompilation, smali modification, repackaging, and Frida dynamic hooking, with on-demand switching to so/native analysis. Prefer locally installed jadx, apktool, frida, adb, ida-reverse, radare2.
binary-diff
Cross-version symbol migration and binary diffing. Use this when you have symbols/reverse engineering results from an old version and need to quickly migrate them to a new version. Applicable scenarios: kernel missing PDB with derivation from old-version symbols, batch-migrating function names after a program update…
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…