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/andrewbartels1/solidworksmcp-python/claude-mdgit clone --depth 1 https://github.com/andrewbartels1/SolidworksMCP-pythonWhat 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.03710 | $0.03710 |
| Opus 5 | $0.01855 | $0.01855 |
| Sonnet 5 | $0.00742 | $0.00742 |
| Haiku 4.5 | $0.00371 | $0.00371 |
Grade B, and why
SolidworksMCP-python 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- A BOM on `~/.claude/settings.json` makes Claude Code silently drop **all** How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SolidWorks MCP Server (Python)
This file is the quick orientation guide for contributors and coding agents.
Platform and Runtime
- Primary runtime is Python 3.13+.
- Real COM automation requires Windows + SolidWorks installed.
- Cross-platform development is possible in mock/test mode.
Build and Development Commands
Use either micromamba environment commands or local virtualenv commands.
Preferred PowerShell workflow
# Show command help
.\dev-commands.ps1
# Full install in micromamba env
.\dev-commands.ps1 dev-install
# Fast test pass (no SolidWorks-required tests)
.\dev-commands.ps1 dev-test
# Full test run including real SolidWorks integration
.\dev-commands.ps1 dev-test-full
# Lint and format
.\dev-commands.ps1 dev-lint
.\dev-commands.ps1 dev-format
# Docs build/serve
.\dev-commands.ps1 dev-docs-build
.\dev-commands.ps1 dev-docs-strict
.\dev-commands.ps1 dev-docs-audit
.\dev-commands.ps1 dev-docs
Virtualenv direct workflow
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install --upgrade pip setuptools wheel
.\.venv\Scripts\python.exe -m pip install -e ".[dev,test,docs]"
# Run server
.\.venv\Scripts\python.exe -m solidworks_mcp.server
# Lint/tests/docs
.\.venv\Scripts\python.exe -m ruff check src tests
.\.venv\Scripts\python.exe -m pytest tests -m "not solidworks_only"
.\.venv\Scripts\python.exe -m mkdocs build --clean
Architecture
- Server entrypoint:
src/solidworks_mcp/server.py - CLI entrypoint:
src/solidworks_mcp/server_cli_fixed.py - Adapters:
src/solidworks_mcp/adapters/pywin32_adapter.py: real SolidWorks COM adapter (Windows)mock_adapter.py: mock adapter for tests and CI-like runsfactory.py: adapter selection/routing logic
- Tools:
src/solidworks_mcp/tools/(modeling, sketching, drawing, export, analysis, automation, templates, VBA, docs discovery) - Agent harness:
src/solidworks_mcp/agents/(prompt schemas, smoke test CLI, run/error persistence)
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.
- 2d ago First seen · 334 lines · 3,710 tokens per session scan B 1d4687e33f0d
SolidworksMCP-python CLAUDE.md is an instructions file published in the GitHub repository andrewbartels1/SolidworksMCP-python (65 stars, last pushed 6d ago), licensed MIT. It adds 3,710 tokens to every session, about $0.0186 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
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).
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.