Borrowing it
Nothing to install: this file belongs to luckiday/vibe-hardware. 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/luckiday/vibe-hardware/main/AGENTS.mdgit clone --depth 1 https://github.com/luckiday/vibe-hardwareWrote 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/luckiday/vibe-hardware/agents-md)<a href="https://agentmods.dev/instructions/luckiday/vibe-hardware/agents-md"><img src="https://agentmods.dev/badge/instructions/luckiday/vibe-hardware/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.
<a href="https://agentmods.dev/instructions/luckiday/vibe-hardware/agents-md"><img src="https://agentmods.dev/badge/instructions/luckiday/vibe-hardware/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01748 | $0.01748 |
| Opus 5.5 | $0.00699 | $0.00699 |
| Sonnet 5.5 | $0.00350 | $0.00350 |
| Haiku 4.5 | $0.00175 | $0.00175 |
Grade A, and why
vibe-hardware 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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents working in this repo. Keep this short — the detailed
method and gotchas for any task live in the relevant skill's SKILL.md +
references/. Read those before acting; this file is the map and the rules.
Repo map
skills/ the agent skills (one per dir):
vibe-plm the integration layer: product manifest + interface contracts
vibe-firmware · vibe-pcb · vibe-cad the three domains (each a self-contained loop)
vibe-uiflow firmware's cheaper operating point: UIFlow2/MicroPython UI devices
vibe-industrial-design appearance before structure: fixed constraints → AI look image
(received from the owner, or generated from the current render) →
measured params → three.js scene → contact sheet → Blender finals
→ versioned ID report
vibe-voice the human channel: speak the hands-on steps (bring-up, probing,
test-fitting) instead of writing them where they won't be read
<skill>/SKILL.md frontmatter (name + "use when…") + the method
<skill>/references/ deep lessons / gotchas, loaded on demand
<skill>/scripts/ portable bash/python tools (plm_check, pcb_check, pcb_view, cad_viewer, …)
examples/ worked end-to-end builds (pager-buddy, …); product.yaml + the three dirs
docs/ getting-started and friends
The three domains are coupled only through data — the contract files named in a
product's product.yaml (vibe-plm owns it), never by one skill calling another's code.
Repo rules
- Keep root guidance short. Put domain detail in the skill it belongs to, not here.
- Skills are self-contained. A skill's code (its
scripts/) must not import or call another skill's code. Prose "hand off to the sibling skill" pointers are fine; a runtime dependency between skills is not. (vibe-pcb's viewer renders in-page; it does not shell out tovibe-cad.) - Generate by script, review in the browser. Sources of truth are small
generator/parametric files (KiCad via
gen_*.py; build123d.py) — never hand-edited GUI binaries. Review interactively onlocalhost, never by booting a heavyweight GUI. If a change needs the GUI to use, it isn't done. - Keep it general; no proprietary designs. Skills teach a reusable method,
illustrated with generic parts. Worked product designs go in
examples/(only what you choose to publish) — never bake a private design into a skill. - Living docs. When a real build teaches a new gotcha/fix/better-practice, fold it back into the skill and commit it with the work. Compounding the experience is the point.
- Global by default. Non-English text is fine where it belongs — language fixtures
in code, quoted strings, log excerpts, translated docs. Keep the shared docs
readable in English, and put a translation in a
*.<lang>.mdbeside its original rather than in place of it.
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.
- 1mo ago Changed · +3 lines · +80 tokens per session c37bb0cbf76c
- 1mo ago First seen · 106 lines · 1,668 tokens per session scan A 7479370f3746
vibe-hardware AGENTS.md is an instructions file published in the GitHub repository luckiday/vibe-hardware (7 stars, last pushed 1mo ago), licensed MIT. It adds 1,748 tokens to every session, about $0.0070 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.