Borrowing it
Nothing to install: this file belongs to ollo12-prog/recallchecker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ollo12-prog/recallchecker/main/CLAUDE.mdgit clone --depth 1 https://github.com/ollo12-prog/recallcheckerWrote 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/instructions/ollo12-prog/recallchecker/claude-md)<a href="https://agentmods.dev/instructions/ollo12-prog/recallchecker/claude-md"><img src="https://agentmods.dev/badge/instructions/ollo12-prog/recallchecker/claude-md.svg" alt="Measured on agentmods" 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.00892 | $0.00892 |
| Opus 5 | $0.00446 | $0.00446 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
recallchecker CLAUDE.md 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — RecallChecker
Instructions for Claude Code sessions in this repo. See README.md for what the project does and ROADMAP.md for build status.
What this is
A free web tool + reference pages + MCP server answering "Is this vehicle recalled?" using the keyless U.S. NHTSA recalls API. Three surfaces share one lookup core.
Tech stack
- Framework: Next.js (App Router) + React, TypeScript.
- Hosting: Cloudflare Workers via the OpenNext adapter (
@opennextjs/cloudflare) — both the web app and the MCP server (a second Worker). Not Cloudflare Pages (its Next.js adapter is deprecated/Edge-only); OpenNext on Workers gives the full Node.js runtime + App Router. - Cache: Workers KV, behind a runtime-agnostic cache port (memory fallback in dev/test).
- No database, no auth, no payments. Stateless lookups + cached responses.
Build with
next build --webpack— Next's Turbopack output triggers aChunkLoadErrorunder OpenNext.
Architecture rule (important)
The recall-lookup logic lives in ONE shared module at src/lib/recalls/ (imported as
@/lib/recalls). The website and the MCP server both import it — never duplicate lookup
logic. Normalize every data source into a single Recall shape so the UI and the MCP tool are
source-agnostic.
index.tsis the runtime-agnostic barrel — import this from the MCP Worker.server.tsis OpenNext-coupled (getCloudflareContext) — web app only.
Data source
- NHTSA Recalls API —
api.nhtsa.gov/recalls/recallsByVehicle?make=&model=&modelYear=. No API key. Date formatDD/MM/YYYY. Quirk: it intermittently returns HTTP 400 for valid no-match queries with a{Count:0,results:[]}body — treat the body as authoritative for 2xx and that 400, but let 5xx fail so an outage isn't masked as "no recalls." - Always display the data's "as of" date and a link to the official NHTSA notice. Data sourced from NHTSA (nhtsa.gov).
Conventions
- Verify any external API behavior, prices, or availability live before relying on it — don't trust assumptions about a third-party API's shape.
- Keep scope tight; validate the data source before building UI (see ROADMAP Phase 0).
- Windows host, but the shell is git-bash: use POSIX/bash syntax with forward slashes
(
mkdir -p,&&,/c/...). Don't default to PowerShell.
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.
- 6d ago First seen · 69 lines · 892 tokens per session scan A a4d9ca78c9a6
recallchecker CLAUDE.md is an instructions file published in the GitHub repository ollo12-prog/recallchecker (0 stars, last pushed 3mo ago), licensed MIT. It adds 892 tokens to every session, about $0.0045 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.