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/fpt/go-dev-mcp/claude-mdgit clone --depth 1 https://github.com/fpt/go-dev-mcpWrote 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/fpt/go-dev-mcp/claude-md)<a href="https://agentmods.dev/instructions/fpt/go-dev-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/fpt/go-dev-mcp/claude-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 | $0.00573 | $0.00573 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
go-dev-mcp CLAUDE.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 4d 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.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Essential Commands
Build and Install
make build # Build the application to output/godevmcp
make install # Install to $GOPATH/bin/godevmcp
Testing and Quality
make test # Run all unit tests with verbose output
make fmt # Format code using gofumpt and golangci-lint
make lint # Run golangci-lint for code quality checks
Development
make run # Run the application in serve mode
make inspect # Run with MCP inspector for debugging
Architecture Overview
GoDevMCP is a Model Context Protocol (MCP) server that provides Go development tools. The architecture follows clean architecture principles:
Core Components
- main.go: Entry point using Google's subcommands pattern
- internal/subcmd/: Subcommand implementations (serve, tree, datetime, etc.)
- internal/mcptool/: MCP tool handlers and registration
- internal/app/: Core business logic for each tool
- internal/infra/: Infrastructure services (filesystem, GitHub API, HTTP client)
- internal/repository/: Data access layer implementations
MCP Tools Architecture
The server registers multiple tools in internal/mcptool/register.go:
get_current_datetime: Current date/timerun_make: Execute make targets with intelligent output filteringtree_dir: Directory structure visualizationsearch_godoc/read_godoc: Go documentation toolssearch_github_code/get_github_content/tree_github_repo: GitHub integrationsearch_local_files: Local file content search
Key Patterns
- Each tool has a handler in
internal/mcptool/that delegates to business logic ininternal/app/ - Infrastructure concerns are abstracted through interfaces in
internal/repository/ - Subcommands provide CLI access to tools for testing/debugging
- The server supports both stdio and SSE modes for different MCP clients
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.
- 4d ago First seen · 70 lines · 573 tokens per session scan A 96898b052e55
go-dev-mcp CLAUDE.md is an instructions file published in the GitHub repository fpt/go-dev-mcp (14 stars, last pushed 19d ago), licensed MIT. It adds 573 tokens to every session, about $0.0029 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
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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.