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/cybergarage/go-matter/copilot-instructionsgit clone --depth 1 https://github.com/cybergarage/go-matterWrote 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/cybergarage/go-matter/copilot-instructions)<a href="https://agentmods.dev/instructions/cybergarage/go-matter/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/cybergarage/go-matter/copilot-instructions.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 | $0.01006 | $0.01006 |
| Opus 5 | $0.00503 | $0.00503 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
go-matter copilot-instructions.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 3d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for go-matter
Specification & Reference
go-matter implements Matter Specification Version 1.5. Code comments cite relevant spec sections (e.g., // 2.5.2. Vendor Identifier). The implementation is based on the official C++ reference: https://github.com/project-chip/connectedhomeip.
Build, Test, and Lint
# Format, vet, lint, then test with coverage
make test
# Steps individually
make format # gofmt + version.go generation
make vet # go vet
make lint # golangci-lint
make install # build and install matterctl CLI, regenerate doc/matterctl.md
# Run a single test
go test -v -run TestName ./matter/...
go test -v -run TestName ./mattertest/...
# Run all tests without linting
go test -v -p 1 -timeout 10m -cover -coverpkg=github.com/cybergarage/go-matter/matter/... \
-coverprofile=matter-cover.out \
github.com/cybergarage/go-matter/matter/... \
github.com/cybergarage/go-matter/mattertest/...
The Makefile pipeline is: format → vet → lint → test. make test runs all steps.
Architecture
go-matter is a Go library implementing the Matter smart home protocol. The module root is github.com/cybergarage/go-matter.
Package Layout
| Package | Role |
|---|---|
matter/ |
Core public interfaces and type aliases (entry point for users) |
matter/ble/ |
BLE transport — BTP (Bluetooth Transport Protocol), Central/scanner |
matter/mdns/ |
mDNS discovery of commissionable devices |
matter/encoding/ |
Encoding: base38, tlv, message (frame format), qr, pairing |
matter/protocol/mrp/ |
Message Reliability Protocol (acknowledgement, session) |
matter/protocol/pase/ |
PASE commissioning handshake (SPAKE2+) |
matter/crypto/ |
Elliptic curve, SPAKE2+, PBKDF, signature primitives |
matter/types/ |
Fundamental Matter types (VendorID, ProductID, Discriminator, …) |
matter/errors/ |
Shared error definitions |
matter/io/ |
Transport interface abstraction |
mattertest/ |
Integration tests (a separate Go package; not in matter/) |
cmd/matterctl/ |
CLI built with Cobra + Viper |
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.
- 3d ago First seen · 73 lines · 1,006 tokens per session scan A 986a1139b614
go-matter copilot-instructions.md is an instructions file published in the GitHub repository cybergarage/go-matter (40 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,006 tokens to every session, about $0.0050 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-09-02.
Other instructions, from other repositories
unraid-management-agent copilot-instructions.md
Copilot instructions for ruaan-deysel/unraid-management-agent, covering copilot instructions, copilot workflow, path-specific instructions, reusable prompts and quick commands.
wombatt GEMINI.md
Gemini CLI instructions for gonzalop/wombatt, a project described as: A tool for monitoring batteries and inverters.
sigrok-mcp-server CLAUDE.md
Instructions for KenosInc/sigrok-mcp-server, covering claude.md, documentation language, project overview, language & build and code style.
ufo-mcp-server CLAUDE.md
Claude Code instructions for rhoegg/ufo-mcp-server, covering claude.md, 📸 screenshots, 🔰 objective, 📐 design guard-rails and 🛠 coding checklist.
dingtalk-workspace-cli AGENTS.md
AGENTS.md instructions for DingTalk-Real-AI/dingtalk-workspace-cli, covering repository agent guide, build and test, command framework declaration, flag / help / schema homology and agent schema contract.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.