HAbedini-qspice-mcp: Instructions file for Codex

AGENTS.md

HAbedini-qspice-mcp AGENTS.md is an instructions file for Codex, OpenCode from kh6570/HAbedini-qspice-mcp. It costs 1,361 tokens per session, scanned A, original, MIT.

A setup guide for connecting the QSpice MCP server to Cursor or Visual Studio Code on Windows. MCP is a way for an editor or agent to connect to an external tool or service.

In plain words
What is it for?
Use it to install and configure the QSpice connection, select Cursor or VS Code, choose the workspace and executable, restart the editor, and run a connection check.
Why use it?
It explains where the connection is registered, how to merge it with existing settings, and how to verify that the editor can reach QSpice.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is kh6570/HAbedini-qspice-mcp's own configuration. It tells Codex and OpenCode how to work on HAbedini-qspice-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything HAbedini-qspice-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/kh6570/HAbedini-qspice-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/kh6570/HAbedini-qspice-mcp

Made for: Codex, OpenCode.

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.

agentmods badge for HAbedini-qspice-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/kh6570/habedini-qspice-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/kh6570/habedini-qspice-mcp/agents-md)
Your own site
<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.

agentmods 80×15 button for HAbedini-qspice-mcp AGENTS.md

Your own site · 80×15
<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>
Per session 1,361 This file is loaded in full into every session.
When invoked 1,361 The same file — it is already loaded in full.
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.

ModelPer sessionOnce 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

Measured 10d ago against content hash 839f759cbe5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

AGENTS.md · 154 lines

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-detect QSPICE64.exe
  • -Clients Cursor | VSCode | Both (default: Both)

Then tell the user:

  1. Fully restart Cursor or VS Code (reload is often not enough after first MCP install).
  2. Open Settings → Tools & MCP and confirm qspice is connected.
  3. 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

  1. Creates .venv in the cloned repo and runs pip install -e .
  2. Detects QSPICE64.exe (or uses -QspiceExe)
  3. Merges qspice into user-level MCP JSON (absolute paths; preserves other servers)
  4. Runs python -m qspice_mcp --describe as 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

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

  1. 10d ago First seen · 154 lines · 1,361 tokens per session scan A 839f759cbe5e

Subscribe to this mod's changes

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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens