Borrowing it
Nothing to install: this file belongs to 0oKevino0/claude-cad. 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/0oKevino0/claude-cad/main/CLAUDE.mdgit clone --depth 1 https://github.com/0oKevino0/claude-cadWrote 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/0okevino0/claude-cad/claude-md)<a href="https://agentmods.dev/instructions/0okevino0/claude-cad/claude-md"><img src="https://agentmods.dev/badge/instructions/0okevino0/claude-cad/claude-md/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/instructions/0okevino0/claude-cad/claude-md"><img src="https://agentmods.dev/badge/instructions/0okevino0/claude-cad/claude-md.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.01488 | $0.01488 |
| Opus 5 | $0.00744 | $0.00744 |
| Sonnet 5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
claude-cad 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 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-cad — notes for Claude Code
This repo is a toolkit and the default workspace. It ships a Claude Code skill, prompts, and docs for generating CadQuery parts whose STEP files reliably open in SolidWorks. The defining idea: never trust generated geometry — verify it before export.
The clone is the workspace (default)
The skill is committed at .claude/skills/cadquery-modeling/, so a fresh clone
arrives with it already active — no install, no reload. The default workflow
is: clone → open in VS Code → describe a part. Parts go in the top-level parts/
(a diagnose.py is shipped there so imports resolve); output lands in output/.
Both are git-ignored, so the user's work stays out of git status and git pull
(to update the toolkit) stays clean.
If someone asks you to model something while this repo is the working directory, that is now the intended path — just do it. Mention the standalone alternative only when it actually fits.
When to suggest a separate project (the alternative)
A standalone project folder elsewhere — set up by pasting
prompts/workflows/project_init.md, producing the three-folder claude-cad/ +
parts/ + output/ layout that examples/sbc-case/ demonstrates — is worth
suggesting when the user wants to:
- version their own designs (the clone git-ignores
parts/, and committing there tangles with toolkitgit pulls), - keep several unrelated projects apart, or
- keep this clone pristine as a reference they
git pullto update.
Don't push it by default; the point of the new layout is that most people never need it.
Helping someone who just arrived
Most people who open Claude Code here have just cloned the repo. The skill is
already active (committed at .claude/skills/), so there's little to set up:
- Point them at
QUICKSTART.md— clone → Python → open in VS Code → confirm the skill is already listed (/skills) → describe a part. Don't re-explain it. - Check their Python —
py -3.11 -c "import cadquery, OCP; print('env OK')". IfOCPfails to import they're on too-new a Python (see below). - Then just build. First part goes in
parts/; run it withpy -3.11 parts/<name>.py; batch-verify withpy -3.11 preflight.py.
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 · 105 lines · 1,488 tokens per session scan A 402dce526440
claude-cad CLAUDE.md is an instructions file published in the GitHub repository 0oKevino0/claude-cad (3 stars, last pushed 1mo ago), licensed MIT. It adds 1,488 tokens to every session, about $0.0074 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
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
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.
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).
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.
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).