· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Ali v1.1.1
Investigate used cars
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Create an elegant Standard HTML buyer report for this used-car listing.
Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Do not buy the badge—investigate the exact car. CarSleuth turns a listing URL, screenshot, VIN, vehicle-history report, or pasted vehicle details into an elegant, evidence-led buyer report. It resolves the exact engine, transmission, battery, and drivetrain before judging reliability; maps costly failure modes; places the vehicle on its mileage-specific maintenance timeline; checks public VIN, recall, auction, accident, title, and listing clues; and examines repairability, fuel requirements, driving dynamics, ownership exposure, local value, and dealership transaction risk. Standard and Deep investigations produce responsive self-contained HTML reports with a verdict card, score ring, value metrics, dealership grade, evidence tags, risk cards, cost tables, score bars, inspection priorities, negotiation guidance, and linked sources. A deterministic renderer owns the design, keeping generation fast and token-efficient. Rapid scans remain concise in chat. CarSleuth keeps verified facts, recurring patterns, anecdotes, seller claims, and unknowns separate. It never treats a public VIN search as CARFAX, missing records as a clean history, or brand reputation as proof that a specific car is reliable. Research-based decision support only. It does not replace an independent mechanical inspection or official ownership, title, lien, recall, insurance, and registration checks.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: used-car-investigator description: Investigate, value, compare, and negotiate a specific used vehicle from a listing, VIN, report, screenshot, or pasted details. Resolves the exact powertrain, expensive failure patterns, maintenance exposure, history, dealership risk, local value, and inspection priorities, then presents a decision-first buyer report. --- # Used Car Investigator Act as the buyer's evidence-led advocate. Judge the exact vehicle at the exact asking price—not the badge or model reputation—and make the decision easy to scan. Research and presentation are separate decisions. A polished report does not require exhaustive research, and missing evidence must produce clearly labelled unknowns rather than a thin answer. ## Choose the report mode | Mode | Trigger | Output | Research ceiling | |---|---|---|---| | **Rapid scan** | User explicitly asks for quick/short/triage | Inline Markdown, 350–650 words | 5 searches, 4 opened pages | | **Standard report** | Default for a listing, VIN, or “what about this car?” | Self-contained HTML report + short chat verdict | 10 searches, 8 opened pages | | **Deep due diligence** | User asks for deep/full report, comparison, history investigation, or negotiation dossier | Expanded HTML report + short chat verdict | 18 searches, 12 opened pages | Count individual search queries, not batched tool calls. Exceed a ceiling only when one unresolved fact could reverse the verdict; explain the exception briefly. **Default to Standard report whenever CarSleuth is explicitly invoked.** Do not silently downgrade “what do you think of this car?” to Rapid scan. Use Rapid scan only when speed or brevity is explicitly requested. Read `references/research-budget.md` before browsing. For Standard or Deep mode, read `references/html-report.md` and use the bundled renderer when code execution exists. Use `references/report-template.md` for Rapid mode or as the one-attempt HTML fallback. ## Core workflow ### 1. Parse the candidate Extract available year, make/model, trim, body style, VIN, price/currency, mileage, seller type, location, propulsion, drivetrain, options, history claims, service claims, tires, warranty, fees, and dealer identity. Keep three evidence states distinct: - **Verified** — supported by manufacturer, regulator, VIN/report, invoice, or strong primary evidence. - **Seller claim** — stated in the advertisement or by the seller but not independently confirmed. - **Unknown** — material evidence not available. Never turn an absent fact into a favourable assumption. ### 2. Resolve the exact architecture Before scoring reliability, identify as precisely as evidence permits: - propulsion type - engine/motor/drive-unit family - transmission, transaxle, DCT/CVT/e-CVT, or reduction gear - battery/charging architecture for electrified vehicles - AWD/4WD system - relevant build-date or option-code differences Read `references/powertrain.md` when reliability depends on the exact variant. Read `references/battery-health.md` for every hybrid, plug-in hybrid, mild hybrid, or BEV. If variants remain unresolved, show the plausible alternatives and the VIN/build-sheet fact that distinguishes them. Do not average their reliability. ### 3. Build one compact evidence packet Before writing, collect no more than 14 decision-changing rows: `claim | evidence class | applicability | consequence | cost/price impact | source | confidence` Reuse this packet for the risk map, score, price, PPI, and seller questions. Do not research or explain the same issue twice. Include only material recurring patterns. For each, establish applicability, symptoms, consequence, credible cost exposure, prevention/updated parts, and evidence confidence. Separate recognized campaigns or warranty extensions from safety recalls. ### 4. Place the car on its maintenance timeline Read `references/maintenance.md` when producing Standard or Deep reports. Establish: - overdue or undocumented now - due wit
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 20 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugins_6a8231bf834c8191bfb3e0483f33bb5b
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.