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/specs)<a href="https://agentmods.dev/commands/carsxe/carsxe-claude-plugin/specs"><img src="https://agentmods.dev/badge/commands/carsxe/carsxe-claude-plugin/specs/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/specs"><img src="https://agentmods.dev/badge/commands/carsxe/carsxe-claude-plugin/specs.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.00338 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
specs 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 — Vehicle Specifications (VIN Decoder)
Decode the VIN provided in $ARGUMENTS using the CarsXE Specifications API.
Steps
-
Parse $ARGUMENTS to extract:
vin(required): 17-character alphanumeric stringdeepdata(optional): pass"true"to get extended datadisableIntVINDecoding(optional): pass"true"to disable international VIN decoding fallback
-
If no VIN is provided, ask: "Please provide a VIN to decode (e.g.,
/carsxe:specs WBAFR7C57CC811956)." -
Make an HTTP GET request:
GET https://api.carsxe.com/specs?key=<CARSXE_API_KEY>&vin=<VIN>&source=claude_plugin[&deepdata=true][&disableIntVINDecoding=true]Replace
<CARSXE_API_KEY>with the value of the environment variableCARSXE_API_KEY. -
Present the response in a clean, readable format including:
- Make, Model, Year, Trim
- Engine details (type, cylinders, displacement, horsepower)
- Transmission & drivetrain
- Fuel type & economy
- Body style & dimensions
- Equipment & features (if available)
-
Handle errors gracefully (invalid VIN, missing API key, etc.).
Notes
- A valid VIN is exactly 17 characters (letters and numbers, no I, O, or Q).
- Remind the user to set the
CARSXE_API_KEYenvironment variable if auth fails.
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 · 36 lines · 0 tokens per session scan A f69c77823f9c
specs is a command published in the GitHub repository carsxe/carsxe-claude-plugin (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 338 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
get-flow-run
Inspect a Postman Flow run by its Run ID — per-block logs, failing block, and status.
uninstall
Remove flow-next files from project.