DEVELOPERS / AGENT SKILLS
YOUR AGENT. A CLEAR WORKFLOW.
Give your agent a repeatable way to work with proxy resources, from checking an account to verifying a browser connection.
No installable USM Skill yet
Explore this pageInstructions guide the agent. Your permissions define its scope.
THE WEBCheck the release before installing
USM Proxy Skills for Claude and Codex are planned. No public installation package or list of supported hosts is available yet. A mention of Claude or Codex is not a claim that every CLI, desktop or cloud environment is supported.
| Host | USM release | Installation |
|---|---|---|
| Claude | Not released | No public package |
| Codex | Not released | No public package |
Start with resources you already own
For a first task, confirm the account, inspect an existing proxy and verify the result before changing anything. The browser or script used by the agent still needs its own proxy configuration.
- State the task, allowed resources and requested country.
- Start with a read-only check of the intended account.
- Configure the tool that opens the web page.
- Verify the actual exit IP and inspect a small sample result.
Separate reading from making changes
Permission to inspect usage is different from permission to buy, renew or replace a proxy. For a paid operation, specify the product, quantity, term and maximum amount first.
A Skill’s instructions are not a substitute for enforced account permissions. Only capabilities and safeguards verified for a released version can be relied on.
| Task | What to establish |
|---|---|
| Inspect proxy details or usage | Correct account and minimum read permissions |
| Configure a browser or script | Which workspace and connection settings may change |
| Purchase, renew or replace | Explicit scope, price and confirmation requirements |
One task can involve several services
Proxy charges follow the selected IP or GB plan. Claude, Codex, browsers and other tools are billed separately by their providers. Installing a Skill does not make those services free.
Updates, removal and troubleshooting
Use the source and version instructions supplied with the release. When reporting a problem, include the host application, Skill version, failed step and a redacted error.
When you stop using an integration, remove its configuration and revoke credentials that are no longer required. Removing instruction files alone does not revoke an API key.
A CONNECTION THAT FITS