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 afishyke/Logisim-Evolution-MCP-Server --skill logisim-evolutiongit clone --depth 1 https://github.com/afishyke/Logisim-Evolution-MCP-ServerWrote 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/afishyke/logisim-evolution-mcp-server/logisim-evolution)<a href="https://agentmods.dev/skills/afishyke/logisim-evolution-mcp-server/logisim-evolution"><img src="https://agentmods.dev/badge/skills/afishyke/logisim-evolution-mcp-server/logisim-evolution.svg" alt="Measured on agentmods" 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.00067 | $0.03059 |
| Opus 5 | $0.00034 | $0.01529 |
| Sonnet 5 | $0.00013 | $0.00612 |
| Haiku 4.5 | $0.00007 | $0.00306 |
Grade A, and why
logisim-evolution 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 6d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logisim-evolution MCP
Use the logisim_* MCP tools for saved Logisim-evolution projects. Do not
claim an operation used MCP if the tools were unavailable. If a newly installed
server is not visible, ask the user to restart OpenCode instead of importing
the server's internal JavaScript classes or editing .circ XML directly.
Standard Workflow
- Call
logisim_get_statusbefore the first operation. Confirm the executable, workspace root, version, and write-validation setting. - Resolve the project path with
logisim_list_projectswhen the user did not give an exact path. Keep every path inside the configured workspace. - When a working source circuit already exists, prefer
logisim_copy_circuitover rebuilding it component by component. - Call
logisim_inspect_projectbefore changing an existing project. Its component and wire indexes are the only reliable indexes for update/remove calls. - Call
logisim_describe_componentbefore using unfamiliar attributes or semantic ports. Do not guess names, direction, width, or geometry. - For a new project, call
logisim_create_projectwithoverwrite: false. Only overwrite an existing file when the user explicitly requests it. - For an empty circuit made from supported components, prefer
logisim_layout_graph. Supply semantic components and directed connections; let the engine place and route the whole graph atomically. - When coordinates are already known, use
logisim_apply_batchfor component and wire arrays. Do not issue dozens of individual add calls or write raw XML. - Use individual component and wire tools only for a genuinely small edit.
- Inspect the finished circuit, then call
logisim_validate_project. - Verify combinational behavior with
logisim_truth_tableor an exhaustivelogisim_test_vector. Treat nonzero failed-vector counts as a failed test even if Logisim exits with status 0. - Call
logisim_launch_guionly after validation and requested simulation pass. Report the saved project path and test result to the user.
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.
- 6d ago First seen · 268 lines · 67 tokens per session scan A a21a6fcab516
logisim-evolution is a skill published in the GitHub repository afishyke/Logisim-Evolution-MCP-Server (2 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 3,059 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
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.