Borrowing it
Nothing to install: this file belongs to Menghuan1918/gemini-cli-gopls. 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/Menghuan1918/gemini-cli-gopls/main/GEMINI.mdgit clone --depth 1 https://github.com/Menghuan1918/gemini-cli-goplsWrote 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/menghuan1918/gemini-cli-gopls/gemini-md)<a href="https://agentmods.dev/instructions/menghuan1918/gemini-cli-gopls/gemini-md"><img src="https://agentmods.dev/badge/instructions/menghuan1918/gemini-cli-gopls/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.00966 | $0.00966 |
| Opus 5 | $0.00483 | $0.00483 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
gemini-cli-gopls 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 8d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The gopls MCP server
These instructions describe how to efficiently work in the Go programming language using the gopls MCP server.
Init a Go workspace
If no go.mod is detected at startup, the gopls MCP will not start. After initializing the Go workspace, you need to restart the CLI for the gopls MCP to take effect.
Detecting a Go workspace
At the start of every session, you MUST use the go_workspace tool to learn about the Go workspace. The rest of these instructions apply whenever that tool indicates that the user is in a Go workspace.
Go programming workflows
These guidelines MUST be followed whenever working in a Go workspace. There are two workflows described below: the 'Read Workflow' must be followed when the user asks a question about a Go workspace. The 'Edit Workflow' must be followed when the user edits a Go workspace.
You may re-do parts of each workflow as necessary to recover from errors. However, you must not skip any steps.
Read workflow
The goal of the read workflow is to understand the codebase.
-
Understand the workspace layout: Start by using
go_workspaceto understand the overall structure of the workspace, such as whether it's a module, a workspace, or a GOPATH project. -
Find relevant symbols: If you're looking for a specific type, function, or variable, use
go_search. This is a fuzzy search that will help you locate symbols even if you don't know the exact name or location. EXAMPLE: search for the 'Server' type:go_search({"query":"server"}) -
Understand a file and its intra-package dependencies: When you have a file path and want to understand its contents and how it connects to other files in the same package, use
go_file_context. This tool will show you a summary of the declarations from other files in the same package that are used by the current file.go_file_contextMUST be used immediately after reading any Go file for the first time, and MAY be re-used if dependencies have changed. EXAMPLE: to understandserver.go's dependencies on other files in its package:go_file_context({"file":"/path/to/server.go"})
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.
- 8d ago First seen · 53 lines · 966 tokens per session scan A c2d88347ea4f
gemini-cli-gopls GEMINI.md is an instructions file published in the GitHub repository Menghuan1918/gemini-cli-gopls (13 stars, last pushed 11mo ago), licensed MIT. It adds 966 tokens to every session, about $0.0048 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-30.
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.