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 fireostendere/mcp_diptrace --skill release-gategit clone --depth 1 https://github.com/fireostendere/mcp_diptraceWrote 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/fireostendere/mcp_diptrace/release-gate)<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/release-gate"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/release-gate.svg" alt="Measured on agentmods" 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.00042 | $0.00677 |
| Opus 5 | $0.00021 | $0.00338 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
release-gate 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 8d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release gate
Return PASS only for the exact requested revision and declared review scope. A green MCP run is
not fab-house approval or DipTrace-format certification.
Use public tools/list for exact callable names and get_capabilities for document/configured
feature availability.
Workflow
- Call
diptrace_status,get_capabilities, andget_document_info; record the exact SHA-256. - Select profiles by document kind:
- PCB:
run_board_review,run_drc,run_connectivity_check,run_manufacturing_review,run_assembly_review,run_testability_review,run_bom_review, andrun_thermal_review; supplement withanalyze_release_readinessfor bounded DFM/DFA/DFT findings available from exported XML (it supplements, not replaces, DipTrace sign-off). - schematic:
run_schematic_review,run_erc,run_connectivity_check, andrun_bom_review.
- PCB:
- Compare each result against the implemented/partial/missing matrix in
REVIEW_ENGINE.md. - Deduplicate by check ID and stable object identity. Preserve waivers, DNP state, explicit
no-connects, confidence, approximation flags, and every
skippeddisclosure. - Decide
PASSonly when no critical/error finding remains, all caller-mandatory implemented checks ran, the SHA stayed stable, and every unavailable category was accepted as outside scope. - Otherwise decide
BLOCKEDand list the shortest evidence-producing next actions. - Emit
../shared/result.schema.json; put the decision in summary and as a finding, not in the transportstatus.
Quantitative boundaries
- Confidence is bounded from 0 through 1 but cannot overrule evidence class.
- Results are paged/bounded; follow resource URIs and truncation metadata rather than assuming the first 100 findings are complete.
- Document identity is a 64-character lowercase SHA-256.
- The server's write limits are 100 operations and 500 conservatively counted affected objects/elements per write, but this gate is read-only.
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.
- 8d ago First seen · 52 lines · 42 tokens per session scan A 67b0b6a8c6c4
release-gate is a skill published in the GitHub repository fireostendere/mcp_diptrace (22 stars, last pushed 4d ago), licensed Apache-2.0. It adds 42 tokens to every session and 677 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-30.
Other skills, from other repositories
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
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.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
ros2-robotics
Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles…
code-plan
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
SmartHome Video Anomaly Benchmark
VLM evaluation suite for video anomaly detection in smart home camera footage.