Borrowing it
Nothing to install: this file belongs to kaneg/k8s-mcp-go. 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/kaneg/k8s-mcp-go/main/AGENTS.mdgit clone --depth 1 https://github.com/kaneg/k8s-mcp-goWrote 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/kaneg/k8s-mcp-go/agents-md)<a href="https://agentmods.dev/instructions/kaneg/k8s-mcp-go/agents-md"><img src="https://agentmods.dev/badge/instructions/kaneg/k8s-mcp-go/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/kaneg/k8s-mcp-go/agents-md"><img src="https://agentmods.dev/badge/instructions/kaneg/k8s-mcp-go/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.00282 | $0.00282 |
| Opus 5 | $0.00141 | $0.00141 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
k8s-mcp-go 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 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.
What it actually says
Agent Guidelines
Avoid Local-Only Fixes
Before changing a local behavior, first decide whether it represents a broader pattern.
For API, schema, MCP tool, permission, or output-format changes:
- Search for peer implementations.
- Identify the shared contract.
- Propose the consistent rule.
- Apply the rule to the representative set, not only the first symptom.
- If intentionally scoped narrowly, state why.
In this repo, MCP tool inputs and outputs should be treated as a tool-surface contract. Keep namespaced resource behavior, output formats, permission exposure, and truncation/full-detail controls consistent across similar tools.
Design Tools For AI Use
MCP tools should be easy for an AI agent to choose and use correctly.
For every tool:
- Make the description explicit about scope, defaults, and important options.
- Prefer schema-visible parameters over hidden string conventions.
- Return output that helps the next tool choice, such as namespace, kind, controller/owner, selectors, and related resource names.
- Use concise structured text or explicit
json/yamlmodes instead of vague prose. - When a tool returns an error, include actionable context when possible, not only the raw Kubernetes error.
If an agent has to guess the resource kind, namespace scope, or next lookup from a tool result, improve the tool contract.
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 · 30 lines · 282 tokens per session scan A 995093e1371f
k8s-mcp-go AGENTS.md is an instructions file published in the GitHub repository kaneg/k8s-mcp-go (2 stars, last pushed 2mo ago), licensed MIT. It adds 282 tokens to every session, about $0.0014 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-31.
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.