What is check-my-proxies?

A health-check workflow for Coronium mobile proxies. It reports whether proxies are active, degraded, dead, or expired, and can test selected proxies more directly.

Listing proxy health, current IPs, expiry dates, connectivity results, and recommendations, then requesting a fresh IP for a proxy that is not working.

It gives a single overview of proxy problems instead of requiring each connection to be checked manually. It also keeps passwords and rotation tokens out of the health summary.

check-my-proxies — Skill for Claude Code by coroniumio

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.

Any agent

npx skills add coroniumio/coronium-proxy-mcp --skill check-my-proxies

Clone the repo

git clone --depth 1 https://github.com/coroniumio/coronium-proxy-mcp

Made for: Claude Code.

Or install coronium-mobile-proxies, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/coroniumio/coronium-proxy-mcp/check-my-proxies/github.svg)](https://agentmods.dev/skills/coroniumio/coronium-proxy-mcp/check-my-proxies)

Your own site

<a href="https://agentmods.dev/skills/coroniumio/coronium-proxy-mcp/check-my-proxies"><img src="https://agentmods.dev/badge/skills/coroniumio/coronium-proxy-mcp/check-my-proxies/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/coroniumio/coronium-proxy-mcp/check-my-proxies"><img src="https://agentmods.dev/badge/skills/coroniumio/coronium-proxy-mcp/check-my-proxies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 829 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00052	$0.00829
Opus 5.5	$0.00021	$0.00332
Sonnet 5.5	$0.00010	$0.00166
Haiku 4.5	$0.00005	$0.00083

Measured 10d ago against content hash 57e5122947af, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

check-my-proxies scanned grade A with 0 findings 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 10d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/coronium-mobile-proxies/skills/check-my-proxies/SKILL.md · 43 lines

How it starts

The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Check my proxies

A health check across the user's Coronium proxies, from overview to fix. Only use the Coronium tools this plugin provides. Do not call a tool the user's request does not need.

1. Overview

Call coronium_get_proxy_health once for the health snapshot of all owned proxies.
Call coronium_get_proxies for names, countries and expiry dates. If the user named a country, pass country_code.
Summarise in a short list, one line per proxy: name, country, the health status (active, degraded, dead or expired) and recommendation as returned, current IP if known, and expiry date. Put problems first. Flag any proxy that expires within 7 days.

Do not print usernames, passwords or rotation tokens in the overview. Connection details belong to the connect-my-proxy skill.

If the user has no proxies, say so and point them to https://dashboard.coronium.io to get one. Do not quote prices unless asked.

2. Test

The health snapshot is evidence, not proof. When the user wants to know whether a specific proxy really works, or agrees to test the ones that look unhealthy, call coronium_test_modem for each of those proxies (one at a time). Report the protocol and result exactly as returned. A listed SOCKS5 port is not proof that SOCKS5 works.

3. Fix with a rotation

Rotation asks the carrier for a fresh IP. Offer it when a proxy is online but slow, blocked by a site the user is testing, or failing the test.

Before rotating, tell the user: "Rotating gives this proxy a new IP. Open connections through it drop for about 10 to 60 seconds." Ask for an explicit yes.
Only after the user agrees, call coronium_rotate_modem with the proxy and confirm: true. Rotate one proxy per approval.
Read the result:
- A new IP: report the old and new IP.
- rotating or pending: the rotation is still running. Call coronium_get_rotation_status after about 30 seconds and report what it says. Never start another rotation while one is pending, and never treat a pending rotation as a failure. Check the status at most three times, then tell the user it is still running and stop. If the status says failed, report the failure and its reason; do not keep polling.
- The IP did not change: the attempt ran but the carrier returned the same IP. The user can try again after the cooldown.
- Refused with HTTP 429: the proxy is in its cooldown between rotations. Tell the user how long to wait, using retry_after_seconds or the wait time in the error message, or about a minute when neither is given. Do not retry on your own.
- Any other error: show the message and stop.
Never retry a rotation automatically, and never replace, restart or reconfigure a proxy as a recovery step unless the user asks for that specific action.

Read the full file on GitHub · 43 lines

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.

10d ago First seen · 43 lines · 52 tokens per session scan A 57e5122947af

Subscribe to this mod's changes

check-my-proxies is a skill published in the GitHub repository coroniumio/coronium-proxy-mcp (1 stars, last pushed 11d ago), licensed MIT. It adds 52 tokens to every session and 829 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-18.

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens