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 kh6570/HAbedini-qspice-mcp --skill qspice-getting-startedgit clone --depth 1 https://github.com/kh6570/HAbedini-qspice-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/kh6570/habedini-qspice-mcp/qspice-getting-started)<a href="https://agentmods.dev/skills/kh6570/habedini-qspice-mcp/qspice-getting-started"><img src="https://agentmods.dev/badge/skills/kh6570/habedini-qspice-mcp/qspice-getting-started/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/kh6570/habedini-qspice-mcp/qspice-getting-started"><img src="https://agentmods.dev/badge/skills/kh6570/habedini-qspice-mcp/qspice-getting-started.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.00084 | $0.01692 |
| Opus 5 | $0.00042 | $0.00846 |
| Sonnet 5 | $0.00017 | $0.00338 |
| Haiku 4.5 | $0.00008 | $0.00169 |
Grade A, and why
qspice-getting-started 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 12d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QSpice: Getting Started
How to drive the QSpice MCP server productively. QSpice is a circuit simulator; this server exposes schematic authoring, simulation, and waveform analysis as MCP tools. Read this first when you pick up any QSpice task.
Core mental model
.qschis the source of truth. Netlists (.net/.cir), logs (.log), and waveforms (.qraw) are derived — regenerate them from the schematic rather than editing them by hand.- Staged analysis siblings are derived too. Tools like
prepare_transientwrite*-tran.qsch(and similar) as copies ofsource_pathplus one directive. They do not auto-sync when you edit the base schematic in the GUI. Edit layout on the base.qschonly; re-runprepare_*before simulating; never treat*-tran.qschas the layout master or open it in the GUI for placement. - Bounded results.
read_waveformis capped (≈2000 points). Prefermeasure_waveformfor scalars (peak, RMS, settling) over dumping raw samples. - Sandbox. All paths resolve against the server's workspace root. Use relative
paths or pass
workspace_rootper call. - Degraded gracefully. Optional backends (waveform reader, schematic editor,
QUX exporter, DLL toolchain) may be missing. Call
describe_server_capabilitiesfirst when anything fails unexpectedly — it reports which tool groups are healthy, partial, or degraded and why.
First step: check the environment
Before non-trivial work, call describe_server_capabilities. It tells you:
whether QSpice is configured, which optional backends are available, which tool
groups are degraded, and feature flags. This avoids guessing when a later tool
returns a backend error.
Two ways to get a circuit
Track B — start from a bundled reference recipe (preferred when one fits)
list_reference_circuit_recipes— see available canonical circuits (id + title).describe_reference_circuit_recipe— read one recipe's manifest, file list, and topology digest to confirm it matches the goal.materialize_reference_circuit— copy the recipe's.qsch(+ sidecars like a C++ DLL source) into the workspace.- Optional:
list_workflow_instructions→read_workflow_instructionfor a step-by-step build/run prompt tied to that recipe.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 137 lines · 84 tokens per session scan A aeb77eb9b3fc
qspice-getting-started is a skill published in the GitHub repository kh6570/HAbedini-qspice-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 1,692 once invoked, about $0.0004 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.