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 skills add w1ne/kernelCAD-web --skill render-inspectgit clone --depth 1 https://github.com/w1ne/kernelCAD-webWrote 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/skills/w1ne/kernelcad-web/render-inspect)<a href="https://agentmods.dev/skills/w1ne/kernelcad-web/render-inspect"><img src="https://agentmods.dev/badge/skills/w1ne/kernelcad-web/render-inspect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/w1ne/kernelcad-web/render-inspect"><img src="https://agentmods.dev/badge/skills/w1ne/kernelcad-web/render-inspect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01304 |
| Opus 5.5 | $0.00018 | $0.00522 |
| Sonnet 5.5 | $0.00009 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00130 |
Grade A, and why
render-inspect 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 26d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
render-inspect
Purpose
kernelcad evaluate returns diagnostics[]. Each entry carries code,
message, severity, and hint. This sub-skill is a quick lookup: given a
diagnostic code seen during a from-reference build, what is the most likely
cause and what is the fix.
Do NOT re-derive this from the code or message alone — read the hint field
first. It is a one-sentence imperative. This sub-skill is for when the hint is
not enough.
Categories of diagnostics in from-reference builds
1. Missing feature — the referenced operation does not exist yet
These diagnostics mean a feature the model depends on was not authored or was accidentally removed:
| Code | Typical cause in from-reference | Fix |
|---|---|---|
recompute.input.missing |
A feature's upstream shape (e.g., the blockout primitive) was renamed or removed. | Call why_did_this_fail MCP tool to walk the chain. Restore or rename the upstream shape. |
feature.face-ref.removed |
A boolean removed a face that a downstream fillet/shell still references. | Reorder: apply the fillet before the boolean. Or switch to a query-based selector. |
feature.face-ref.ambiguous-after-split |
A boolean split a face that was targeted by name. | Apply the feature before the splitting boolean, or use await selectEdges(shape, query) to target the specific post-split face. |
2. Wrong argument — the operation exists but the input is out of range
| Code | Typical cause in from-reference | Fix |
|---|---|---|
feature.invalid-args |
Fillet radius exceeds the local edge geometry (too large for a thin frame arm). | Reduce the fillet radius. Use the variable-radius form to apply a smaller radius on narrow edges. |
feature.invalid-args (scale) |
.scale([sx, sy, sz]) received a zero or negative factor (e.g., a param reached 0). |
Add a min: 0.001 guard on the controlling param. |
feature.hole.no-target-face |
The hole's entry face is correct but the bore axis does not intersect a solid body. | Check that the target body extends along the bore axis past the hole entry depth. |
feature.hole.cut-missing |
A bore centre is off the entry face, the depth is zero, or material is still on the bore axis after the cut. | (u, v) are mm from the face centre, not world coordinates. Use the face centre and span in the message: u = worldU - centreU, v = worldV - centreV. |
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.
- 26d ago Changed · +1 lines f6f927f47500
- 1mo ago First seen · 89 lines · 46 tokens per session scan A 647f3db2cf7e
render-inspect is a skill published in the GitHub repository w1ne/kernelCAD-web (33 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,304 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
solidworks-mcp
Build, edit, inspect and export native SolidWorks models through solidworks-mcp. Use for CAD modeling, raster-to-sketch work and SolidWorks COM/MCP diagnostics. Read before calling a SolidWorks MCP tool.
simplecadapi
Build, assemble, inspect, reconstruct, and export parametric CAD models with the SimpleCADAPI Python SDK. Use for SimpleCAD geometry modeling, constrained sketches, parts and assemblies, standard gears and bearings, STEP/BREP inspection and reconstruction, vector-PDF drawing reconstruction, durable product packages…
aieng-cad-authoring
Active MCP-first CAD authoring skill for AIENG Workbench. Use when the user asks to create, design, draft, model, or iteratively build CAD geometry through the active cad. MCP tools. Do not use for solver/result review, schema/library implementation, or editing legacy IR plans.
bridge-troubleshooting
Diagnose figma-mcp-rust connection problems. Use when tools fail with "plugin not connected", requests time out, the port is already in use, or the Figma plugin cannot reach the MCP server. Covers installing the companion Figma plugin, port 1994, and running multiple MCP clients.
aieng-closed-loop-copilot
MCP-first closed-loop CAD/CAE copilot skill for improving an existing solved design against explicit targets. Use when the user asks for bounded design iteration using editable CAD parameters, solver reruns, and evidence-backed comparison.
rhino
Automate Rhino modeling through RhinoCommon, work with Grasshopper data trees, and configure Rhino.Compute workflows.