everyproxy — Claude Code skill: proxy tasks and setup
This Claude Code skill uses the EveryProxy REST API to manage traffic packages. It activates for package lookups, authorized proxy orders, provisioning checks, and credential delivery.
Apache-2.0 ★ 681 updated 2026-10-24
npx skills add everyinfra/everyinfra-agent-plugins --skill everyproxy -a claude-codeWhat everyproxy does
The skill reads the proxy catalog and filters packages by traffic amount, proxy kind, region, and optional sticky duration. It can place an order for a rotating or sticky allocation, then check provisioning status. Orders are paid, and the selected package and region require user authorization.
Requests use the shared EveryInfra key in EVERYINFRA_API_KEY and go to https://api.everyinfra.com with Bearer authentication. A delivered password can be exposed once. Credentials must go only to a secret destination approved by the user, never to chat, logs, or project files.
What it helps with
- find proxy packages by region and kind
- order an authorized rotating or sticky allocation
- check provisioning without placing a purchase
- retrieve one-time proxy credentials
Example prompts for the agent
- List proxy packages for the requested region and kind.
- Order an authorized sticky proxy allocation in the selected region.
- Check this proxy order's status without starting another purchase.
How to install everyproxy
1Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everyproxy -a claude-code2Manually: put the files in place
~/.claude/skills/everyproxy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/everyproxy/
1Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everyproxy -a codex2Manually: put the files in place
.agents/skills/everyproxy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everyproxy -a cursor2Manually: put the files in place
.cursor/skills/everyproxy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install everyinfra/everyinfra-agent-plugins plugins/everyinfra/skills/everyproxy2Manually: put the files in place
.github/skills/everyproxy/SKILL.md1Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everyproxy -a gemini-cli2Platform CLI
gemini skills install https://github.com/everyinfra/everyinfra-agent-plugins --path plugins/everyinfra/skills/everyproxyManually: put the files in place
.devin/skills/everyproxy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add everyinfra/everyinfra-agent-plugins --skill everyproxy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about everyproxy
How do I install everyproxy in Claude Code?
Run npx skills add everyinfra/everyinfra-agent-plugins --skill everyproxy -a claude-code. The skill file is at ~/.claude/skills/everyproxy/SKILL.md.
What does everyproxy do?
It uses EveryProxy's REST API to inspect traffic packages, place proxy orders, check provisioning, and retrieve credentials.
What does everyproxy need to work?
It needs the shared EveryInfra key in EVERYINFRA_API_KEY and access to https://api.everyinfra.com. Proxy orders are paid and require user authorization for the package and region.
Source text
SKILL.md · Apache-2.0
---
name: everyproxy
description: Use EveryProxy traffic-package REST APIs with the shared EveryInfra key. Use when the user wants to inspect proxy packages, order an authorized rotating or sticky proxy allocation, check provisioning status, or retrieve one-time proxy credentials.
---
# EveryProxy
EveryProxy is REST-only in the current plugin. Do not invent an MCP tool for it. Use
`https://api.everyinfra.com` with `Authorization: Bearer $EVERYINFRA_API_KEY`.
1. Read the free `GET /api/v1/proxy/catalog` response. Select a live package by `gb`, `kind`,
`region` and optional `sticky_minutes`; pricing is by traffic, never by session minutes.
2. `POST /api/v1/proxy/order` is a paid order and may return credentials immediately. The user's
request must authorize the package and region before ordering.
3. For asynchronous provisioning, inspect `GET /api/v1/proxy/order/{order_id}` without `deliver`.
Status inspection must not be turned into a purchase.
4. Use `?deliver=1` only when the user intends to accept delivery and the charge. Delivery can expose
the password exactly once.
5. Move credentials only to the user-approved secret destination. Never print them in normal chat,
command logs, screenshots, source files or Git history.
6. Report order status and billing separately. If delivery failed and was refunded, create a new
order only with user authorization.
© everyinfra · Apache-2.0 · everyinfra/everyinfra-agent-plugins