What is testpoint-planner?

A planning workflow for adding standalone test pads to a PCB, a circuit board, so a fixture can probe selected electrical connections.

Use it to inspect a DipTrace PCB, find test-point candidates, preview and validate a guarded transaction, and review design-rule, connectivity, and testability results.

It helps measure and improve explicit test-point coverage while preserving excluded or sensitive circuit nets and checking the planned board changes.

testpoint-planner — Skill for Claude Code and Codex by fireostendere

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.

Any agent

npx skills add fireostendere/mcp_diptrace --skill testpoint-planner

Clone the repo

git clone --depth 1 https://github.com/fireostendere/mcp_diptrace

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/testpoint-planner/github.svg)](https://agentmods.dev/skills/fireostendere/mcp_diptrace/testpoint-planner)

Your own site

<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/testpoint-planner"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/testpoint-planner/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/testpoint-planner"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/testpoint-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 891 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00077	$0.00891
Opus 5.5	$0.00031	$0.00356
Sonnet 5.5	$0.00015	$0.00178
Haiku 4.5	$0.00008	$0.00089

Measured 28d ago against content hash 87a7f5d0c164, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testpoint-planner 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 28d 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.

skills/testpoint-planner/SKILL.md · 62 lines

How it starts

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

Read runtime access before choosing between explicit-path MCP, a live bridge session, and native/headless CLI. Their availability is separate.

Testpoint planner

RAG: engineering memory by default — shared workflow. Consult measurement/DFT material for probe loading, coverage and fixture access, and DipTrace guidance when selecting the placement/connection workflow.

Plan only explicit MCP/DipTrace standalone-pad testpoints; reported coverage is not a fixture-access simulation. Use public tools/list for exact callable names and get_capabilities for document/configured feature availability.

Workflow

Call diptrace_status, get_capabilities, and get_document_info; require a PCB and freeze its SHA-256.
Use list_testpoints and review_testpoint_coverage for the exact net scope. Preserve excluded, sensitive, high-speed, RF, clock, reset, and user-locked nets.
Call find_testpoint_candidates with explicit side, probe diameter, clearance, grid, and candidates per net. Ask the operator when fixture-side access or sensitive-net policy is absent.
Stage add_testpoints(..., dry_run=true) in a transaction. Never commit from a request for a plan.
Inspect preview_transaction, then validate_transaction. When placement is authorized, commit with expected_sha256; retain authorization already given for the selected scope.
A testpoint's net assignment is logical membership, not proof of copper connection. Inspect pads/traces/vias around candidates, route required short stubs with route_connection, or verify the same-net pour after native refill. Re-run run_review with profiles dft_basic, drc_basic, and connectivity. Revert only this session's failed changes with a current hash guard.
Emit ../shared/result.schema.json.

Quantitative boundaries

candidates_per_net is 1 through 100; the free-grid search is bounded to 5,000 candidate points.
The API defaults are probe diameter 1.0 mm, clearance 0.5 mm, and grid 2.54 mm. They are search parameters, not universal fixture rules; expose them and let the operator override them.
Each transaction accepts at most 100 operations and 500 conservatively counted affected objects/elements; this can be fewer than 500 unique physical objects.
All distances are millimetres regardless of root Units.

Read the full file on GitHub · 62 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.

28d ago Changed · +1 lines · +35 tokens per session 87a7f5d0c164
1mo ago Changed · +10 lines · +4 tokens per session 4d7a24ef7ec3
2mo ago First seen · 51 lines · 38 tokens per session scan A 67fb89fedae3

Subscribe to this mod's changes

testpoint-planner is a skill published in the GitHub repository fireostendere/mcp_diptrace (25 stars, last pushed 24d ago), licensed Apache-2.0. It adds 77 tokens to every session and 891 once invoked, about $0.0003 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.

Hardware and IoT

testpoint-planner next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
testpoint-plannerfireostendere/mcp_diptrace	Skill	25	24d ago	Apache-2.0	A	77	Claude Code, Codex
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
jetson-diagnosticNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code, Codex
holoscan-install-wheelNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	34	Claude Code, Codex
offensive-z-waveSnailSploit/Claude-Red	Skill	10k	25d ago	MIT	A	113	Claude Code, Codex
doca-socket-relayNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	236	Claude Code, Codex
hsb-flashNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	B	94	Claude Code