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 agentmods add instructions/ariklapid/pyslang-mcp/agents-mdgit clone --depth 1 https://github.com/ariklapid/pyslang-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/ariklapid/pyslang-mcp/agents-md)<a href="https://agentmods.dev/instructions/ariklapid/pyslang-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ariklapid/pyslang-mcp/agents-md.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.01439 | $0.01439 |
| Opus 5 | $0.00720 | $0.00720 |
| Sonnet 5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
pyslang-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 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is the public contributor and agent guidance for pyslang-mcp.
Read this first, then read README.md,
CONTRIBUTING.md, and
REMOTE_DEPLOYMENT.md when the task touches
deployment.
Mission
Build a professional, open-source MCP server that gives AI systems
compiler-backed, read-only understanding of Verilog and SystemVerilog projects
through pyslang.
The product is a semantic analysis MCP, not an EDA runtime. Keep scope tight and technically honest.
Product Scope
The public tool surface is:
pyslang_parse_filespyslang_parse_filelistpyslang_get_diagnosticspyslang_list_design_unitspyslang_describe_design_unitpyslang_get_hierarchypyslang_find_symbolpyslang_find_memberpyslang_get_assignmentspyslang_trace_connectivitypyslang_get_instance_connectionspyslang_summarize_diagnostics_by_codepyslang_dump_syntax_tree_summarypyslang_preprocess_filespyslang_get_project_summary
Planned tools are not part of the public tool surface until implemented, tested, and documented.
Current Implementation Plan
Issue #15 Verilog analysis work has a public-safe implementation plan at docs/superpowers/plans/2026-06-11-verilog-mcp-functions.md.
When executing that plan:
- follow the plan task-by-task and update checkboxes as work completes
- implement
pyslang_find_member,pyslang_get_assignments,pyslang_trace_connectivity,pyslang_get_instance_connections, andpyslang_summarize_diagnostics_by_code - do not implement
pyslang_parse_generated_cacheas part of that plan - do not advertise planned tools as released behavior until the code, tests, docs, and MCP protocol smoke coverage are complete
- preserve the read-only, project-root, bounded-output, and cache invariants in this file
Non-goals:
- simulation
- synthesis
- waveform viewing
- testbench generation
- RTL editing or refactoring through MCP tools
- remote code execution
- full IDE or language-server parity
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 · 170 lines · 1,439 tokens per session scan A 6befb7ddf089
pyslang-mcp AGENTS.md is an instructions file published in the GitHub repository ariklapid/pyslang-mcp (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,439 tokens to every session, about $0.0072 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-30.
Other instructions, from other repositories
cml-mcp AGENTS.md
AGENTS.md instructions for xorrkaz/cml-mcp, covering agents.md — cml mcp server, project overview, compatibility goal, repository layout and tool modules (src/cmlmcp/tools/).
brilliant_sdk AGENTS.md
Instructions for brilliantlabsAR/brilliant_sdk, covering brilliant sdk — agent guide, how an app works (the pattern behind everything), minimal reading paths, verify without hardware and testing.
NeoMind CLAUDE.md
Claude Code instructions for camthink-ai/NeoMind, covering neomind — edge ai platform for iot, development commands, ecosystem repositories, extension package contract (.nep) and device type template contract (json).
cad-cae-copilot copilot-instructions.md
Copilot instructions for armpro24-blip/cad-cae-copilot, covering github copilot — aieng workspace and essentials.
phone-mcp CLAUDE.md
Claude Code instructions for premex-ab/phone-mcp, covering claude.md, project overview, build commands, architecture and module layout.
zmk-config AGENTS.md
AGENTS.md instructions for urob/zmk-config, covering customization guide, ground rules, how the multi-board layout works, adding a new board and where to change what.