Borrowing it
Nothing to install: this file belongs to oaslananka/kicad-studio-kit. 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/oaslananka/kicad-studio-kit/main/AGENTS.mdgit clone --depth 1 https://github.com/oaslananka/kicad-studio-kitWrote 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/oaslananka/kicad-studio-kit/agents-md)<a href="https://agentmods.dev/instructions/oaslananka/kicad-studio-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/oaslananka/kicad-studio-kit/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.01273 | $0.01273 |
| Opus 5 | $0.00636 | $0.00636 |
| Sonnet 5 | $0.00255 | $0.00255 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
kicad-studio-kit 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KiCad Studio Kit Agent Instructions
This file is the repository-local contract for coding agents. Follow higher-priority
system and operator instructions first, then these repo rules. Any MCP-capable client or
coding agent that consumes this repository should treat AGENTS.md as the canonical
repository instructions.
Repository Boundaries
- Canonical repo:
oaslananka/kicad-studio-kit. - Product surfaces:
apps/vscode-extension: KiCad Studio VS Code extension.packages/test-harness: private shared test utilities.
- The MCP server lives in a separate repository — see KiCad MCP Pro.
- Do not introduce another canonical repository or release root.
- Keep issue scope narrow. Do not mix unrelated issues in one branch or PR.
Required First Reads
Before changing behavior, read the relevant source, tests, docs, manifests, and workflow files. For repo-wide orientation, start with:
README.mddocs/architecture/repo-structure.mddocs/architecture/product-boundaries.mddocs/testing-strategy.mddocs/support-matrix.mddocs/release.mddocs/agents/client-configs.mddocs/architecture/protocol-change-checklist.md- MCP server docs (see KiCad MCP Pro)
Local Commands
Use the repository package managers and lockfiles. From the repo root:
Linux/macOS:
corepack pnpm install --frozen-lockfile
corepack pnpm run lint
corepack pnpm run typecheck
corepack pnpm run test
corepack pnpm run build
corepack pnpm run verify:dist
Windows PowerShell:
corepack pnpm install --frozen-lockfile
corepack pnpm run lint
corepack pnpm run typecheck
corepack pnpm run test
corepack pnpm run build
corepack pnpm run verify:dist
Python/MCP server tests run from the KiCad MCP Pro repository.
Repo-policy checks that are often relevant:
corepack pnpm run check:agent-configs
corepack pnpm run check:ci-lanes
corepack pnpm run docs:lint
corepack pnpm run docs:links
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 · 143 lines · 1,273 tokens per session scan A 7a28fd36e219
kicad-studio-kit AGENTS.md is an instructions file published in the GitHub repository oaslananka/kicad-studio-kit (16 stars, last pushed 2d ago), licensed MIT. It adds 1,273 tokens to every session, about $0.0064 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).
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.
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.