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.
git clone --depth 1 https://github.com/carsxe/carsxe-claude-pluginWrote 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.
[](https://agentmods.dev/commands/carsxe/carsxe-claude-plugin/auth)<a href="https://agentmods.dev/commands/carsxe/carsxe-claude-plugin/auth"><img src="https://agentmods.dev/badge/commands/carsxe/carsxe-claude-plugin/auth/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.
<a href="https://agentmods.dev/commands/carsxe/carsxe-claude-plugin/auth"><img src="https://agentmods.dev/badge/commands/carsxe/carsxe-claude-plugin/auth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00437 |
| Opus 5 | $0.00000 | $0.00218 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
auth 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.
What it actually says
CarsXE — Set & Validate API Key
Validate the API key provided in $ARGUMENTS using the CarsXE Auth API. If valid, set it as the CARSXE_API_KEY environment variable for the current session automatically — no manual export or set required.
Steps
-
Parse $ARGUMENTS to extract:
key(required): the CarsXE API key string to validate
-
If no key is provided, ask: "Please provide your CarsXE API key (e.g.,
/carsxe:auth YOUR_API_KEY)." -
Make an HTTP GET request to validate the key:
GET https://api.carsxe.com/v1/auth/validate?key=<KEY>&source=claude_plugin -
Evaluate the response:
- If the response indicates the key is valid (e.g.,
"valid": trueor a success status), proceed to step 5. - If the response indicates the key is invalid or the request fails, tell the user: "The API key provided is invalid. Please check your key and try again." — do not set anything.
- If the response indicates the key is valid (e.g.,
-
Set
CARSXE_API_KEYin the current session by running the appropriate shell command via the terminal tool:- Mac/Linux:
export CARSXE_API_KEY=<KEY> - Windows (cmd):
set CARSXE_API_KEY=<KEY> - Windows (PowerShell):
$env:CARSXE_API_KEY="<KEY>"
Detect the current platform and run the correct command automatically.
- Mac/Linux:
-
Confirm success to the user:
"Your CarsXE API key has been validated and set for this session. You can now use all
/carsxe:*commands."
Notes
- The key is never stored to disk — it is only set in the current shell session.
- If the session ends, the key will need to be set again (or added to the shell profile by the user for persistence).
- This command replaces any previously set
CARSXE_API_KEYin the current session.
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 · 37 lines · 0 tokens per session scan A 179ad66bfa80
auth is a command published in the GitHub repository carsxe/carsxe-claude-plugin (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 437 tokens. 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-08-31.
Other commands, from other repositories
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
search
Discover APIs across your Postman workspaces. Ask natural language questions about available endpoints and capabilities.
sync
Sync Postman collections with your API code. Create collections from specs, push updates, keep everything in sync.
docs
Generate, improve, and publish API documentation from Postman collections.
generate-spec
Generate or update an OpenAPI spec from your codebase.
trigger-flow
Trigger (run) a deployed Postman Flow with inputs, and deploy-then-trigger it if it isn't deployed yet.