Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/cedrickchee/text-to-cad/agents-mdgit clone --depth 1 https://github.com/cedrickchee/text-to-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/cedrickchee/text-to-cad/agents-md)<a href="https://agentmods.dev/instructions/cedrickchee/text-to-cad/agents-md"><img src="https://agentmods.dev/badge/instructions/cedrickchee/text-to-cad/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 | $0.00981 | $0.00981 |
| Opus 5 | $0.00491 | $0.00491 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
text-to-cad 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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository is a harness for script-driven CAD generation with coding agents like Codex and Claude Code.
If you are modifying CAD Explorer itself, go to .agents/skills/cad/explorer/README.md.
Skill Routing
Use the bundled skills for workflow details:
.agents/skills/cad/SKILL.mdfor STEP, STL, 3MF, DXF, GLB/topology artifacts, render images, and@cad[...]prompt references..agents/skills/urdf/SKILL.mdfor generated URDF files,gen_urdf(), robot links, joints, limits, and URDF mesh references..agents/skills/robot-motion/SKILL.mdfor ROS 2/MoveIt dependency setup, running the motion server, and generating IK/path-planning artifacts for an existing URDF.
Use the URDF skill when generating or editing a robot description. If an existing valid URDF already exists, the robot-motion skill can attach motion artifacts to it directly; use robot-motion for inverse kinematics, path planning, motion artifact generation, and motion-server testing.
AGENTS.md is intentionally harness-focused. Reusable CAD, URDF, and robot-motion workflow rules live inside the skills.
Harness Context
Project CAD files are repo-relative. This harness does not reserve a
project-file directory. Project CAD entries may live at the repository root
under folders such as STEP/, STL/, DXF/, and 3MF/, or in another
explicit repo-relative layout chosen by the project.
The CAD and URDF skill tools are file-targeted. They do not depend on a harness layout or prepend a project root.
Project-specific context may live in compact root-level notes such as
PROJECT.md. Do not copy reusable generator contracts, prompt-reference rules,
validation policy, Explorer/link rules, image review policy, or full CLI syntax
into them; link to the relevant skill references instead.
For CAD Explorer scan-root, link, and @cad[...] behavior, defer to
.agents/skills/cad/SKILL.md and its Explorer/rendering references.
Python Environment
Prefer the repo-local CAD runtime when it exists:
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.
- 5d ago First seen · 79 lines · 981 tokens per session scan A acbfd8f3b507
text-to-cad AGENTS.md is an instructions file published in the GitHub repository cedrickchee/text-to-cad (23 stars, last pushed 3mo ago), licensed MIT. It adds 981 tokens to every session, about $0.0049 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
text-to-cad AGENTS.md
AGENTS.md instructions for earthtojake/text-to-cad, covering agents.md, branch and layout first, release workflow, repo map and repo rules.
text-to-cad CLAUDE.md
Claude Code instructions for earthtojake/text-to-cad, a project described as: A library of agent skills for CAD, CAE and CAM.
step.parts AGENTS.md
Instructions for earthtojake/step.parts, covering agent guide, quick commands, repo shape, adding parts and metadata rules.
CADCLAW AGENTS.md
AGENTS.md instructions for sunnyday-technologies/CADCLAW, covering agents.md — guidance for ai assistants using cadclaw, what cadclaw is, and what it is not, the core rule: place authored parts, don't generate them, why this rule exists and what you may generate.
solidworks-api-skill CLAUDE.md
Instructions for guoleizhen717/solidworks-api-skill, covering solidworks api skill repository, repository purpose, skill scope and project conventions.
step.parts CLAUDE.md
Instructions for earthtojake/step.parts, a project described as: 12,000+ open source STEP parts for your next CAD project.