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/lien)<a href="https://agentmods.dev/commands/carsxe/carsxe-claude-plugin/lien"><img src="https://agentmods.dev/badge/commands/carsxe/carsxe-claude-plugin/lien/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/lien"><img src="https://agentmods.dev/badge/commands/carsxe/carsxe-claude-plugin/lien.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.00236 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
lien 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 — Lien & Theft Check
Check for active liens and theft records on a vehicle using the VIN provided in $ARGUMENTS.
Steps
- Parse $ARGUMENTS to extract the VIN (required).
- If no VIN is provided, ask: "Please provide a VIN to check for liens and theft records (e.g.,
/carsxe:lien WBAFR7C57CC811956)." - Make an HTTP GET request:
ReplaceGET https://api.carsxe.com/v1/lien-theft?key=<CARSXE_API_KEY>&vin=<VIN>&source=claude_plugin<CARSXE_API_KEY>with the value of the environment variableCARSXE_API_KEY. - Present the results clearly:
- Active lien status (yes/no)
- Lien holder details if applicable
- Theft record status (stolen / not stolen)
- Any related dates or jurisdiction info
- Highlight any active liens or theft records prominently as they are critical for buyers.
- Handle errors gracefully (invalid VIN, no data, auth error).
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 · 21 lines · 0 tokens per session scan A 2c4f7843524e
lien 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 236 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
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.