Borrowing it
Nothing to install: this file belongs to cybergarage/go-matter. 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/cybergarage/go-matter/main/GEMINI.mdgit 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/gemini-md)<a href="https://agentmods.dev/instructions/cybergarage/go-matter/gemini-md"><img src="https://agentmods.dev/badge/instructions/cybergarage/go-matter/gemini-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.00717 | $0.00717 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
go-matter GEMINI.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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini Context: go-matter
This project is a Go implementation of the Matter connectivity standard for smart home and IoT devices.
Project Overview
- Core Library: Located in the
matter/directory, providing interfaces for Commissioners, Commissionees, and Devices. - CLI Tool:
matterctl(incmd/matterctl/) for scanning and pairing Matter devices. - Transports: Supports BLE (Bluetooth Low Energy) and mDNS (Multicast DNS) for device discovery.
- Encoding: Implements Matter-specific encodings including TLV (Tag-Length-Value), Base38, and Message Frame formats.
- Security: Includes implementations for PASE (Passcode-Authenticated Session Establishment) and PAKE (Password-Authenticated Key Exchange).
Key Technologies
- Language: Go
- CLI Framework: Cobra and Viper
- Logging:
github.com/cybergarage/go-logger - External Dependencies:
github.com/cybergarage/go-ble: BLE communication.github.com/cybergarage/go-mdns: mDNS service discovery.
Architecture
The project follows a modular structure:
matter/: Core interfaces and common types.matter/ble/: BLE transport protocol and scanning.matter/mdns/: mDNS service discovery.matter/encoding/: Data encoding and decoding (TLV, Base38, QR, Message).matter/crypto/: Cryptographic primitives.matter/protocol/: Higher-level protocols (MRP, PASE).mattertest/: Comprehensive test suites and helpers.
Building and Running
The project uses a Makefile for common tasks.
Build and Install
- Install
matterctlCLI:
Or directly via Go:make installgo install ./cmd/matterctl
Development Commands
- Format Code:
make format(runsgofmt) - Lint:
make lint(runsgolangci-lint) - Vet:
make vet(runsgo vet) - Test:
make test(runs tests with coverage) - Clean:
make clean
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.
- 5d ago First seen · 70 lines · 717 tokens per session scan A acbaeea3f08b
go-matter GEMINI.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 717 tokens to every session, about $0.0036 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
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.