Borrowing it
Nothing to install: this file belongs to sunnyday-technologies/CADCLAW. 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/sunnyday-technologies/CADCLAW/main/AGENTS.mdgit clone --depth 1 https://github.com/sunnyday-technologies/CADCLAWWrote 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/sunnyday-technologies/cadclaw/agents-md)<a href="https://agentmods.dev/instructions/sunnyday-technologies/cadclaw/agents-md"><img src="https://agentmods.dev/badge/instructions/sunnyday-technologies/cadclaw/agents-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.01753 | $0.01753 |
| Opus 5 | $0.00877 | $0.00877 |
| Sonnet 5 | $0.00351 | $0.00351 |
| Haiku 4.5 | $0.00175 | $0.00175 |
Grade A, and why
CADCLAW AGENTS.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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — guidance for AI assistants using CADCLAW
You are an AI assistant working inside (or on behalf of) a project that uses CADCLAW. This file is the load-bearing policy for how you should behave when adding or editing CAD geometry. Read it before any geometry-touching work.
Before editing this repository at all, read
AGENTS_GIT_PROTOCOL.md. More than one agent works here from more than one clone. GitHub is the shared memory; your working copy is not. Fetch first, commit what you validate, never force-push.
What CADCLAW is, and what it is not
CADCLAW is an assembly and validation tool for STEP assemblies and BOMs. Two halves, both first-class:
- Assemble.
cadclaw assemblecompiles a declarative assembly spec into a STEP file. It resolves authored STEP sources, seats each part by connector frames and datum chains (place_relative_to), and writes the assembly plus a design inventory, a model-derived BOM, review renders, and step-by-step build sequences. - Validate. It loads a STEP file and reports findings against rules in
cadclaw.yaml: inventory, interference, adjacency, dimensions, orientation, floating, color, structural, tolerance, BOM-vs-CAD parity, claim-audit, publish-audit.
CADCLAW is not a CAD authoring system. It does not draw parts. It does not own bolt-circle constants, hole-drilling helpers, or NEMA mounting templates.
Hold this distinction precisely: assembling is in scope, authoring is not. Placing a part the user drew is CADCLAW's job. Creating that part's geometry is not. Do not describe CADCLAW as "only a validator" (it builds assemblies) or as a "CAD generator" (it never creates geometry).
The core rule: place authored parts, don't generate them
Default to placement, not generation. The user authors complex
geometry in a native CAD package and exports a STEP. CADCLAW's own assembly
compiler (cadclaw/assembly_compiler.py, driven by an assembly_spec.v0.1
YAML) then places copies of those authored parts into the assembly, and
CADCLAW verifies the placement. An external CadQuery script still works, but
the spec-driven compiler is the supported path.
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 · 170 lines · 1,753 tokens per session scan A 5b983912c1bb
CADCLAW AGENTS.md is an instructions file published in the GitHub repository sunnyday-technologies/CADCLAW (18 stars, last pushed 4d ago), licensed MIT. It adds 1,753 tokens to every session, about $0.0088 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-30.
Other instructions, from other repositories
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).
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).
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.
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.