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/history)<a href="https://agentmods.dev/commands/carsxe/carsxe-claude-plugin/history"><img src="https://agentmods.dev/badge/commands/carsxe/carsxe-claude-plugin/history/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/history"><img src="https://agentmods.dev/badge/commands/carsxe/carsxe-claude-plugin/history.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.00210 |
| Opus 5 | $0.00000 | $0.00105 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
history 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 12d 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 History
Retrieve the history report for a vehicle using the VIN provided in $ARGUMENTS.
Steps
- Parse $ARGUMENTS to extract the VIN.
- If no VIN is provided, ask: "Please provide a VIN to look up the vehicle history."
- Make an HTTP GET request:
ReplaceGET https://api.carsxe.com/history?key=CARSXE_API_KEY&vin={VIN}&source=claude_pluginCARSXE_API_KEYwith the value of the environment variableCARSXE_API_KEY. - Present the history report clearly:
- Ownership history (number of owners, states)
- Accident / damage records
- Title status (clean, salvage, rebuilt, etc.)
- Odometer readings over time
- Service & maintenance records (if available)
- Theft records
- Flag any red flags prominently (e.g., salvage title, multiple accidents).
- Handle errors gracefully.
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.
- 12d ago First seen · 23 lines · 0 tokens per session scan A 23eb094ac920
history is a command published in the GitHub repository carsxe/carsxe-claude-plugin (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 210 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
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
eol-report
EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
t800-onboard
A command for newcomers that explains what is installed in Cursor globally and in the current project, plus what the T-800 team can do.
rvcsi-calibrate
Learn a v0 per-subcarrier baseline (mean amplitude) from a .rvcsi capture.