Borrowing it
Nothing to install: this file belongs to holla2040/ThomsonLint. 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/holla2040/ThomsonLint/main/CLAUDE.mdgit clone --depth 1 https://github.com/holla2040/ThomsonLintWrote 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/holla2040/thomsonlint/claude-md)<a href="https://agentmods.dev/instructions/holla2040/thomsonlint/claude-md"><img src="https://agentmods.dev/badge/instructions/holla2040/thomsonlint/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.03351 | $0.03351 |
| Opus 5 | $0.01675 | $0.01675 |
| Sonnet 5 | $0.00670 | $0.00670 |
| Haiku 4.5 | $0.00335 | $0.00335 |
Grade B, and why
ThomsonLint CLAUDE.md scanned grade B with 1 finding 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 8d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
This ensures `review_instructions.txt` is always up-to-date in the repository, allowing users to immediately use it with their design files without needing to run any scripts. How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
ThomsonLint is a knowledge and rule framework for AI-assisted hardware design review. It provides structured, machine-readable resources that enable AI models to analyze and identify potential issues in hardware designs (schematics and PCB layouts). The tested driver is Claude Code; a single-file-upload bundle exists for web AIs (e.g., Gemini, Claude.ai, ChatGPT) but that workflow has not been validated.
The framework is named after J.J. Thomson, discoverer of the electron, reflecting its goal of uncovering fundamental issues in hardware designs.
Core Components
ontology/ontology.json- Machine-readable JSON defining rules, domains, severity levels, and failure modes for hardware design reviewexamples/examples.json- Practical examples (good and bad) that map to ontology rules, used for training/testing AI understandingdocs/AI_Hardware_Design_Review_KnowledgeBase.md- Human-readable explanations and context for the ontology rulesdocs/Multi_Agent_Reasoning_Spec.md- Specification for multi-agent architecture (Power/SMPS, High-Speed SI, Analog, EMC/ESD, Thermal/Mechanical agents)
Commands
Validate JSON files
pip install jsonschema # if not installed
python validate_json.py
Generate review instructions file
./gen_context.sh > review_instructions.txt
Validate findings coverage (mandatory before report)
python tools/validate_findings.py exports/<project_name>-findings.json
Mechanical coverage gate. Schema-validates the findings file, lists every PDF / schematic / board export in the findings file's directory that is not cited in any evidence[].source, and reports issues missing required fields. Exit code is non-zero if uncited inputs or missing fields are present. Run this before generating the HTML report. This is the gate that prevents the agent from silently dropping datasheet analysis (every PDF the agent opens must end up in the findings file).
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.
- 8d ago First seen · 167 lines · 3,351 tokens per session scan B 134c882eb2f5
ThomsonLint CLAUDE.md is an instructions file published in the GitHub repository holla2040/ThomsonLint (41 stars, last pushed 10d ago), licensed MIT. It adds 3,351 tokens to every session, about $0.0168 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.