Borrowing it
Nothing to install: this file belongs to kh6570/HAbedini-qspice-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kh6570/HAbedini-qspice-mcp/main/AGENTS.mdgit 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/instructions/kh6570/habedini-qspice-mcp/agents-md)<a href="https://agentmods.dev/instructions/kh6570/habedini-qspice-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kh6570/habedini-qspice-mcp/agents-md/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/instructions/kh6570/habedini-qspice-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kh6570/habedini-qspice-mcp/agents-md.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.01361 | $0.01361 |
| Opus 5 | $0.00681 | $0.00681 |
| Sonnet 5 | $0.00272 | $0.00272 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
HAbedini-qspice-mcp AGENTS.md 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 10d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent guide — first-time MCP setup (Windows)
Use this file when the user asks to install, configure, or connect the QSpice MCP server in Cursor or VS Code after cloning this repo.
MCP is registered at user level (available in every project). The setup script merges a qspice entry into existing configs without removing other servers.
| Client | User config path (Windows) |
|---|---|
| Cursor | %USERPROFILE%\.cursor\mcp.json |
| VS Code | %APPDATA%\Code\User\mcp.json |
Quick setup (preferred)
From the cloned repo root in PowerShell:
pwsh -ExecutionPolicy Bypass -File .\scripts\setup_mcp.ps1 -WorkspaceRoot "D:\path\to\your\circuit\folder"
- Omit
-WorkspaceRoot→ defaults to%USERPROFILE%\Desktop\qspice-mcp-test - Omit
-QspiceExe→ auto-detectQSPICE64.exe -Clients Cursor|VSCode|Both(default:Both)
Then tell the user:
- Fully restart Cursor or VS Code (reload is often not enough after first MCP install).
- Open Settings → Tools & MCP and confirm
qspiceis connected. - Optional:
pwsh -ExecutionPolicy Bypass -File .\scripts\verify_mcp.ps1
Smoke prompt:
Call describe_server_capabilities on the qspice MCP server and summarize tool groups.
What the setup script does
- Creates
.venvin the cloned repo and runspip install -e . - Detects
QSPICE64.exe(or uses-QspiceExe) - Merges
qspiceinto user-level MCP JSON (absolute paths; preserves other servers) - Runs
python -m qspice_mcp --describeas a sanity check
Important: The venv stays in the repo you cloned; user-level MCP points at that venv with absolute paths. Re-run setup after moving the repo.
Simulation workspace (--workspace-root) is where .qsch files live — independent of which IDE folder is open.
Agent checklist
| Step | Action |
|---|---|
| 1 | Confirm Windows + Python ≥ 3.11 on PATH |
| 2 | Run scripts/setup_mcp.ps1 with user's circuit folder as -WorkspaceRoot |
| 3 | On failure: install QSpice, pass -QspiceExe, or recreate repo .venv |
| 4 | Ask user to fully restart IDE |
| 5 | Call describe_server_capabilities via MCP |
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.
- 10d ago First seen · 154 lines · 1,361 tokens per session scan A 839f759cbe5e
HAbedini-qspice-mcp AGENTS.md is an instructions file published in the GitHub repository kh6570/HAbedini-qspice-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,361 tokens to every session, about $0.0068 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.