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.
npx skills add carsxe/carsxe-claude-plugin --skill vehicle-recallsgit 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/skills/carsxe/carsxe-claude-plugin/vehicle-recalls)<a href="https://agentmods.dev/skills/carsxe/carsxe-claude-plugin/vehicle-recalls"><img src="https://agentmods.dev/badge/skills/carsxe/carsxe-claude-plugin/vehicle-recalls/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/skills/carsxe/carsxe-claude-plugin/vehicle-recalls"><img src="https://agentmods.dev/badge/skills/carsxe/carsxe-claude-plugin/vehicle-recalls.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.00046 | $0.00260 |
| Opus 5 | $0.00023 | $0.00130 |
| Sonnet 5 | $0.00009 | $0.00052 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
vehicle-recalls 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 yesterday.
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
When the user asks about recalls or safety issues:
- If they have a VIN, call the CarsXE Recalls API:
GET https://api.carsxe.com/v1/recalls?key={CARSXE_API_KEY}&vin={VIN}&source=claude_plugin - If they have year/make/model but no VIN, use the Recalls by YMM API instead (
/v1/recalls-ymm). - If they have many VINs (fleet, inventory, CSV), use the Recalls Batch API (
/v1/recalls-batch/*).
- Present recall details:
- Total number of open recalls
- For each recall: campaign number, component, defect description, remedy status
- If no recalls exist, clearly confirm the vehicle has no open recalls.
- Emphasize any safety-critical recalls.
- If the API key is missing, tell the user to set the
CARSXE_API_KEYenvironment variable.
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.
- yesterday Changed · +3 lines ec68bf9ffce5
- 12d ago First seen · 18 lines · 46 tokens per session scan A 277d95111dd7
vehicle-recalls is a skill published in the GitHub repository carsxe/carsxe-claude-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 260 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
writing-style
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.