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 agents/andrewbartels1/solidworksmcp-python/agent-ui-workflowsgit 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.00000 | $0.00541 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
agent-ui-workflows 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 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.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent UI Workflows (Planning)
This page outlines practical UI options for visually guiding users through agent decisions like hinge selection, sourcing, and printability checks.
Problem to Solve
Prompt-only interaction is powerful but slows down design iteration when users need fast branching choices such as:
- Hinge family: ball-bearing, concealed, piano, living hinge
- Sourcing strategy: McMaster-Carr, local stock, commodity online
- Print strategy: orientation, split/no-split, support policy
Recommended Interaction Patterns
1) FastMCP Choice Cards (MVP)
Use a local web UI that renders pre-baked option cards before generating final tool calls.
Card examples:
- Hinge type card with strength/complexity/printability scores
- Sourcing card with lead time and cost band
- Orientation card with likely support and weakness risks
Advantages:
- Fast to implement
- Easy to test with real users
- Works beside VS Code and SolidWorks
2) VS Code Webview Wizard
A side panel wizard that progressively asks:
- Design intent
- Printer/material profile
- Joint family
- Sourcing preference
- Risk tolerance
Then emits a structured plan and ready-to-run prompts.
3) Hybrid Mode: Wizard + Prompt Console
Keep freeform chat but pair it with visual controls for key branch points.
- Visual UI decides branch options
- Prompt console keeps expert flexibility
UX Blueprint for Prebaked Choices
- Step 1: Requirements intake (load, motion cycle, environment)
- Step 2: Candidate options list with reasons
- Step 3: Simulated outcomes (printability + sourcing)
- Step 4: Tool plan preview (MCP calls and expected artifacts)
- Step 5: Execute and log in SQLite memory
Data Contract for UI Cards
Use a typed card payload so both UI and agents share structure:
{
"category": "hinge_choice",
"options": [
{
"id": "ball_bearing_hinge",
"label": "Ball-Bearing Hinge",
"strength_score": 9,
"printability_score": 5,
"cost_band": "medium",
"source_hint": "McMaster-Carr"
}
]
}
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 · 82 lines · 0 tokens per session scan A d970dc79566b
agent-ui-workflows is an agent published in the GitHub repository andrewbartels1/SolidworksMCP-python (65 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 541 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
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.