Borrowing it
Nothing to install: this file belongs to Spectoda/easyeda-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/Spectoda/easyeda-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/Spectoda/easyeda-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/spectoda/easyeda-mcp/agents-md)<a href="https://agentmods.dev/instructions/spectoda/easyeda-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/spectoda/easyeda-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.00595 | $0.00595 |
| Opus 5 | $0.00298 | $0.00298 |
| Sonnet 5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
easyeda-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 7d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module Overlay: easyeda-mcp
This file adds project-specific instructions for AI agents working in this public repository.
Language
Use English for all project files, issues, commits, pull requests, comments, documentation, and user-facing examples.
Public Repository Boundary
Treat this repository as public at all times.
Never commit:
- credentials, API tokens, browser cookies, OAuth sessions, or
.envfiles; - private EasyEDA account exports;
- Spectoda controller design source files unless they are explicitly published;
- customer-specific manufacturing files;
- internal price agreements, supplier terms, or production-only data.
If a task needs private Spectoda EasyEDA account data, keep that work in the
Spectoda GEN2 workspace and document the mirror target in the internal
datasheets module. This repository may contain only generic import/export
tooling and sanitized examples.
Scope
This module owns the generic EasyEDA Pro MCP server, bridge extension, smoke testing flow, and public developer documentation.
It does not own:
- Spectoda controller source designs;
- Spectoda product identity or pricing;
- internal datasheet catalog mirrors;
- production order approval;
- JLCPCB account credentials or payment workflows.
Engineering Rules
- Prefer typed, narrow MCP tools over raw code execution.
- Keep bridge permissions explicit and auditable.
- Separate read-only inspection tools from write or order-preparation tools.
- Require human confirmation for operations that modify an EasyEDA project, export private data, prepare a manufacturing order, or open an external checkout flow.
- Add tests around protocol contracts before expanding live editor automation.
- Keep public examples synthetic or explicitly open-source.
Browser Testing
When a change touches the EasyEDA extension, editor bridge, or browser workflow,
document the smoke test result. Use Codex Browser Use (browser-use) to
verify the real browser/editor path when feasible. If Browser Use is not
available, mark the browser smoke result as blocked instead of using another
browser workflow.
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.
- 7d ago First seen · 85 lines · 595 tokens per session scan A 372de2f1a47b
easyeda-mcp AGENTS.md is an instructions file published in the GitHub repository Spectoda/easyeda-mcp (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 595 tokens to every session, about $0.0030 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
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).
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.
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.
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).
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.