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 zinntikumugai/rigol-oscilloscope-mcp --skill measurement-workflowsgit clone --depth 1 https://github.com/zinntikumugai/rigol-oscilloscope-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/zinntikumugai/rigol-oscilloscope-mcp/measurement-workflows)<a href="https://agentmods.dev/skills/zinntikumugai/rigol-oscilloscope-mcp/measurement-workflows"><img src="https://agentmods.dev/badge/skills/zinntikumugai/rigol-oscilloscope-mcp/measurement-workflows/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/zinntikumugai/rigol-oscilloscope-mcp/measurement-workflows"><img src="https://agentmods.dev/badge/skills/zinntikumugai/rigol-oscilloscope-mcp/measurement-workflows.svg" alt="Reviewed on agentmods" width="80" 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.00066 | $0.01615 |
| Opus 5 | $0.00033 | $0.00807 |
| Sonnet 5 | $0.00013 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
measurement-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 11d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Oscilloscope Measurement Workflows
Safety first — before ANY measurement
- Confirm the physical setup with the user. The MCP server cannot see probes. Ask the user to confirm: the probe tip is on the intended test point, the ground clip is on a ground reference, and the probe's attenuation switch matches the
probe_ratioyou configure. - Never measure AC mains (line voltage) with a standard probe. If the user asks to probe mains, a primary side of a power supply, or anything referenced to line voltage: refuse and explain that this requires an isolated differential probe. Do not proceed without one, even if asked again — a grounded scope probe on mains can destroy equipment and injure people.
Choosing settings from the signal type
Pick the row matching the signal, then adjust with the user's known values. The coupling / Vpp / freq / trigger / sweep_mode / probe_ratio columns map onto configure_channel / configure_timebase / configure_trigger arguments; the acquire column names the acquisition tool to call afterwards (run or single).
| signal | coupling | assume Vpp | assume freq | trigger | sweep_mode | acquire | probe_ratio | notes |
|---|---|---|---|---|---|---|---|---|
| digital logic | DC | 3.3 V | 1 MHz | rising, Vpp/2 | normal | run | 10 | ask the logic level if unknown |
| uart | DC | 3.3 V | 115200 baud | falling, Vpp/2 | normal | single | 10 | idle-high: the start bit is a falling edge. timebase = 1/baud s/div shows one ~10-bit frame |
| i2c | DC | 3.3 V | 100 kHz (SCL) | falling, Vpp/2 | normal | single | 10 | two lines (SDA/SCL) — probe both, trigger on SDA |
| spi | DC | 3.3 V | 1 MHz (SCLK) | falling (CS assert), Vpp/2 | normal | single | 10 | multiple lines: CS/SCLK/MOSI |
| pwm | DC | 3.3 V | 10 kHz | rising, Vpp/2 | auto | run | 10 | then measure duty and frequency |
| clock | DC | 3.3 V | 10 MHz | rising, Vpp/2 | auto | run | 10 | |
| power ripple | AC | 50 mV | 100 kHz (switching) | rising, 0 V | auto | run | 1 | set bandwidth_limit=true; use a 1x probe with a short ground spring |
| switching PSU (secondary) | DC | 12 V | 100 kHz | rising, Vpp/2 | auto | run | 10 | secondary side only — the primary side is mains-referenced (see safety rule 2) |
| audio | AC | 1 V | 1 kHz | rising, 0 V | auto | run | 10 | |
| unknown signal | DC | 5 V (coarse) | — | none yet; sweep_mode auto, level 0 V | auto | run | 10 | start coarse: 1 ms/div, then follow the exploration workflow below |
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.
- 11d ago First seen · 77 lines · 66 tokens per session scan A 15cbe24f6239
measurement-workflows is a skill published in the GitHub repository zinntikumugai/rigol-oscilloscope-mcp (0 stars, last pushed 13d ago), licensed MIT. It adds 66 tokens to every session and 1,615 once invoked, about $0.0003 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
neuroskill-bci
Use live BCI cognitive and mood state from NeuroSkill.
ruview-advanced-sensing
Advanced RuView capabilities — RuvSense multistatic sensing (attention-weighted fusion, geometric diversity, persistent field model), cross-viewpoint fusion across multiple nodes, RF tomography (ISTA L1 solver, voxel grids), longitudinal biomechanics drift, pre-movement intention signals, adversarial signal detection…
ruview-applications
Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping, Mass Casualty Assessment (MAT), and the 3D point-cloud fusion demo. Use when someone wants to actually do something…
lab-hardware-cad
Design custom laboratory hardware as parametric build123d models and export fabrication-ready STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a research…
opentrons-integration
Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one workflow…
pylabrobot
Develop and review PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Use for PyLabRobot protocols or API questions; keep physical execution behind an explicit operator safety gate.