agent-invocation-reference

A reference with copy-and-paste commands for starting logged SolidWorks design sessions and invoking agents. It includes examples for one-off and interactive, multi-turn sessions.

In plain words
What is it for?
Use it to configure logging, start the SolidWorks MCP server, run an interactive design script, or ask an agent to plan a model reconstruction.
Why use it?
It removes the need to remember environment settings, startup commands, and invocation syntax. This makes repeatable agent runs easier to start.

Agent

Install

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.

agentmods
npx agentmods add agents/andrewbartels1/solidworksmcp-python/agent-invocation-reference
Clone the repo
git clone --depth 1 https://github.com/andrewbartels1/SolidworksMCP-python
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,322 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03322
Opus 5 $0.00000 $0.01661
Sonnet 5 $0.00000 $0.00664
Haiku 4.5 $0.00000 $0.00332

Measured yesterday against content hash 4c36bbe8bbae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-invocation-reference 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 yesterday.

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.

docs/agents/agent-invocation-reference.md · 443 lines

How it starts

The opening of the file, as written. The whole thing — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Invocation Reference — Quick Patterns

This is a reference guide showing exactly how to invoke agents with full logging, including copy-paste command templates.

Quick Copy-Paste Setup

Template 1: One-Off Design Session

# Step 1: Set env vars
$env:SOLIDWORKS_MCP_ENABLE_DB_LOGGING = "true"
$env:SOLIDWORKS_MCP_CONVERSATION_ID = "SESSION_NAME_HERE"
$env:SOLIDWORKS_MCP_RUN_ID_PREFIX = "SESSION_NAME_HERE"

# Example:
$env:SOLIDWORKS_MCP_CONVERSATION_ID = "baseball-bat-rebuild"
$env:SOLIDWORKS_MCP_RUN_ID_PREFIX = "bat-initial"

# Step 2: Start server
.\dev-commands.ps1 dev-run

# Step 3: In VS Code Copilot Chat, ask:
# @solidworks-part-reconstructor: Open the Baseball Bat sample, 
# classify the feature family, and show me the first 10 tool calls 
# needed to rebuild it.

Template 2: Multi-Turn Interactive Session

# Terminal 1: Start server with logging
$env:SOLIDWORKS_MCP_ENABLE_DB_LOGGING = "true"
$env:SOLIDWORKS_MCP_CONVERSATION_ID = "u-joint-assembly"
.\dev-commands.ps1 dev-run

# Terminal 2: Run interactive script
.\.venv\Scripts\python.exe .\scripts\interactive_design.py

interactive_design.py:

import os
from src.solidworks_mcp.agents import (
    insert_conversation_event,
    find_run_timeline,
)

session_id = "u-joint-assembly"
os.environ["SOLIDWORKS_MCP_ENABLE_DB_LOGGING"] = "true"
os.environ["SOLIDWORKS_MCP_CONVERSATION_ID"] = session_id

for pass_num in range(1, 3):
    run_id = f"ujoint-pass-{pass_num}"
    os.environ["SOLIDWORKS_MCP_RUN_ID_PREFIX"] = run_id
    
    print(f"\n=== Pass {pass_num} ===")
    print("Use Claude Code to run tool calls.")
    print(f"Session ID: {session_id}")
    print(f"Run ID: {run_id}")
    
    input("Press Enter when done with this pass...")
    
    timeline = find_run_timeline(run_id)
    print(f"Logged {len(timeline['events'])} events in pass {pass_num}.")

Template 3: Batch Test of Sample Parts

# Test all sample parts with logging
$env:SOLIDWORKS_MCP_ENABLE_DB_LOGGING = "true"

@("Paper Airplane", "Baseball Bat", "U-Joint\pin") | ForEach-Object {
    $part_name = $_
    $env:SOLIDWORKS_MCP_CONVERSATION_ID = "batch-test-$part_name"
    $env:SOLIDWORKS_MCP_RUN_ID_PREFIX = "classify-$part_name"
    
    Write-Host "Testing: $part_name"
    .\.venv\Scripts\python.exe -c `
        "from src.solidworks_mcp.agents import find_conversation_events; `
         print(f'Logged: {len(find_conversation_events(\"batch-test-$part_name\"))} events')"
}

Read the full file on GitHub · 443 lines

Changes

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.

  1. yesterday First seen · 443 lines · 0 tokens per session scan A 4c36bbe8bbae

Subscribe to this mod's changes

agent-invocation-reference is an agent published in the GitHub repository andrewbartels1/SolidworksMCP-python (65 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,322 tokens. 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens