op-proxy

op-proxy is a command for coding agents from ogrodev/fsociety. It costs 12 tokens per session (724 once invoked), scanned A, original, MIT.

A command for configuring proxy chains, VPN connections, Tor routing, and a killswitch that blocks traffic if protected routing fails.

In plain words
What is it for?
Setting up, testing, rotating, checking, or stopping proxy, VPN, and Tor connections.
Why use it?
It helps control how network traffic leaves a system and prevents accidental direct connections when a VPN or Tor route drops.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the trenton plugin — 5 skills, 12 commands, 2 agents shipped together

Install

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.

agentmods
npx agentmods add commands/ogrodev/fsociety/op-proxy
Clone the repo
git clone --depth 1 https://github.com/ogrodev/fsociety

Or install trenton, the plugin that ships this one along with the rest of its 5 skills, 12 commands, 2 agents.

Wrote 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.

agentmods badge for op-proxy

README.md
[![agentmods](https://agentmods.dev/badge/commands/ogrodev/fsociety/op-proxy.svg)](https://agentmods.dev/commands/ogrodev/fsociety/op-proxy)
Your own site
<a href="https://agentmods.dev/commands/ogrodev/fsociety/op-proxy"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/op-proxy.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 724 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00724
Opus 5 $0.00006 $0.00362
Sonnet 5 $0.00002 $0.00145
Haiku 4.5 $0.00001 $0.00072

Measured yesterday against content hash bc789effcf4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

op-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 yesterday.

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.

- Check external IP: `curl -s --socks5 127.0.0.1:9050 ifconfig.me` (Tor) or `curl -s ifconfig.me` (VPN)
trenton/commands/op-proxy.md · 57 lines

What it actually says

Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Proxy Chain Management

Target and options: $ARGUMENTS

  1. Parse $ARGUMENTS for the subcommand (setup, rotate, test, status, or kill) and --chain flag. Dispatch to the appropriate operation.

  2. setup: Configure the full proxy chain:

    • Generate or update /etc/proxychains4.conf with the selected chain type (tor+proxy, direct, multi-hop)
    • Start the Tor service: systemctl start tor and verify SOCKS proxy on port 9050
    • Configure VPN connection (WireGuard via wg-quick up or OpenVPN via openvpn --config)
    • Set up a killswitch via iptables to block all traffic if the VPN/Tor connection drops:
      iptables -A OUTPUT -o tun0 -j ACCEPT
      iptables -A OUTPUT -o lo -j ACCEPT
      iptables -A OUTPUT -d <vpn-server-ip> -j ACCEPT
      iptables -A OUTPUT -j DROP
      
    • Ask the user for VPN credentials or config path via AskUserQuestion if not provided
  3. rotate: Cycle to a new identity/endpoint:

    • Request a new Tor circuit: echo -e 'AUTHENTICATE ""\r\nSIGNAL NEWNYM\r\n' | nc 127.0.0.1 9051
    • Cycle to the next VPN endpoint if multi-hop is configured
    • Flush DNS cache to prevent leaks
    • Verify the new external IP after rotation
  4. test: Verify the proxy chain integrity:

    • Check external IP: curl -s --socks5 127.0.0.1:9050 ifconfig.me (Tor) or curl -s ifconfig.me (VPN)
    • DNS leak test: resolve a unique hostname and verify the DNS server is not the ISP's
    • WebRTC leak check: verify no local IP exposure via WebRTC-capable tools
    • Killswitch verification: temporarily disconnect VPN/Tor and confirm traffic is blocked
  5. status: Display current proxy chain state:

    • Show active proxychains configuration
    • Display Tor circuit path and exit node country
    • Show VPN connection status, endpoint, and assigned IP
    • Display current external IP address
  6. kill: Tear down all proxy infrastructure:

    • Disconnect VPN: wg-quick down or kill OpenVPN process
    • Stop Tor service: systemctl stop tor
    • Remove iptables killswitch rules and restore original network configuration
    • Flush DNS cache
    • Ask the user for confirmation before tearing down via AskUserQuestion
  7. Log all proxy operations to the ops tracker:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/ops-tracker.js" add <target> proxy-chain <subcommand> "<chain-type>" <result> <severity>
    
Changes

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.

  1. yesterday First seen · 57 lines · 12 tokens per session scan A bc789effcf4f

Subscribe to this mod's changes

op-proxy is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 724 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-09-03.

Related

Other commands, from other repositories