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 skills/brs077/cnc-design-control-mcp/gcode-analyzenpx skills add brs077/CNC-design-control-MCP --skill gcode-analyzegit clone --depth 1 https://github.com/brs077/CNC-design-control-MCPWrote 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/brs077/cnc-design-control-mcp/gcode-analyze)<a href="https://agentmods.dev/skills/brs077/cnc-design-control-mcp/gcode-analyze"><img src="https://agentmods.dev/badge/skills/brs077/cnc-design-control-mcp/gcode-analyze.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.1 | $0.00047 | $0.00317 |
| Opus 5 | $0.00023 | $0.00159 |
| Sonnet 5 | $0.00009 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
gcode-analyze 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 6d 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.
What it actually says
G-code Analysis
Analyze loaded G-code without any machine interaction. Completely safe — no motion or state changes.
Available MCP Tools
analyze_gcode— Parse the currently loaded G-code and extract:- Bounding box (X/Y/Z min/max) — verify the cut fits the workpiece
- Move counts — number of rapid (G0) and cutting (G1/G2/G3) moves
- Feed rates — all feed rates used in the program
- Spindle speeds — all spindle speeds used
- Tool changes — any T commands in the program
- Estimated run time — based on move distances and feed rates
Workflow
- Load G-code with
load_gcodefirst - Run
analyze_gcodeto inspect it - Check that the bounding box fits within the machine's work area
- Verify feed rates and spindle speeds are appropriate for the material
- Proceed with
start_jobif everything looks correct
Tips
- Compare the bounding box against your workpiece dimensions
- Check for unexpected Z depths that could damage the spoilboard
- Look for very high or very low feed rates that might indicate errors
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.
- 6d ago First seen · 33 lines · 47 tokens per session scan A 8e14cb1af403
gcode-analyze is a skill published in the GitHub repository brs077/CNC-design-control-MCP (1 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 317 once invoked, about $0.0002 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.