use-transfer-card skill. Neither
route installs a browser extension or opens a separate browser.
The plugin exposes get_agent_card, get_card_details, and
list_agent_transactions. Its card-details tool intentionally returns the
assigned number and expiry to model context and browser arguments. It never
returns CVC or submits payment. Bank controls remain necessary; companion
purchase settings cannot limit a disclosed number.
Build and install the optional package
From the Transfer application repository, run:artifacts/transfer-plugin/ with the current
card worker, compiled client and pinned SDK dependencies. Node.js 20+ and npm are
required. No Playwright, Chromium, account credentials or card details are
included.
Select the intended agent’s private version 3 credential file from a completed
Copy for Codex setup. In your private copy of mcp.json, set the server’s
env.TRANSFER_CARD_CONFIG to that absolute file path before installing. The
unconfigured package exits with a setup message. The plugin reads only that selected connection;
it never searches for a card or chooses an agent automatically. Keep the file
outside the plugin folder and readable only by its owner.
Use the built folder with Codex’s local plugin marketplace workflow, following
the package’s README.md for a complete marketplace example. Installing a local
package and connecting a private credential are separate from publishing in a
public plugin directory. The package has not been publicly published or
automatically installed.
Enable one connection for the intended agent and verify it with
get_agent_card. Avoid enabling the same agent through both the direct setup
and plugin server in one chat. At the checkout, use
get_card_details and the existing browser within the
user’s purchase scope and the host’s permissions.
Official packaging references:
portable plugin layout
and desktop-only stdio plugins.