agentmods.dev

mcp-rancher: Instructions file for Codex

AGENTS.md

mcp-rancher AGENTS.md is an instructions file for Codex, OpenCode from rex/mcp-rancher. It costs 759 tokens per session, scanned A, original, MIT.

Project instructions for building and maintaining a Rancher MCP server. Rancher is software for managing Kubernetes clusters, and MCP lets an agent use tools exposed by a server.

In plain words
What is it for?
Use them when setting up the project, running its development lab, modifying the Python server, and running linting, type checks, tests, validation, and architecture checks.
Why use it?
They give contributors the required setup commands, supported Rancher versions, repository structure, and checks needed before calling the work complete.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is rex/mcp-rancher's own configuration. It tells Codex and OpenCode how to work on mcp-rancher itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-rancher configures →

not rated 1repo changed 2d ago A scan 759 tokens original MIT
View source ↗ rex/mcp-rancher
Reuse

Borrowing it

Nothing to install: this file belongs to rex/mcp-rancher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rex/mcp-rancher/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/rex/mcp-rancher

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for mcp-rancher AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rex/mcp-rancher/agents-md.svg)](https://agentmods.dev/instructions/rex/mcp-rancher/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/rex/mcp-rancher/agents-md"><img src="https://agentmods.dev/badge/instructions/rex/mcp-rancher/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 759 This file is loaded in full into every session.
When invoked 759 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00759 $0.00759
Opus 5 $0.00380 $0.00380
Sonnet 5 $0.00152 $0.00152
Haiku 4.5 $0.00076 $0.00076

Measured 2d ago against content hash f55d22f44ddf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

mcp-rancher 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 2d 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.

AGENTS.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — rancher-mcp

1. Project snapshot

  • What: Capability-aware Rancher MCP server; 230+ tools across discovery, generic fallbacks, and curated operator workflows. Primary target: Rancher 2.9.3 (production). Compat floor: 2.6.5 (devlab) — capability detection bridges the gap; never regress 2.6.5 behavior.
  • Runtime: Python 3.12 · FastMCP · uv · httpx · structlog
  • Non-goals: Does not manage Rancher itself; does not support non-Rancher Kubernetes APIs directly.

2. Setup

make setup        # install deps, copy .env, install pre-commit hooks
cp .env.example .env && $EDITOR .env   # set RANCHER_URL, RANCHER_TOKEN
make dev          # run the MCP server (stdio)
make lab-up       # spin up local Rancher 2.6.5 lab (kind + helm)

3. Commands the agent MUST run before declaring done

  • make lint
  • make typecheck
  • make test
  • make validate (runs all three + architecture check)

4. Repo layout

src/rancher_mcp/     MCP server — tools, models, client, config
tests/               unit/ and integration/ test suites
catalog/             capabilities.yaml — machine-readable tool catalog
devtools/            local lab scripts, mock Rancher server
scripts/             architecture check, fixture capture
docs/                ADRs and supplemental docs

5. Code style

  • One resource family or one operation family per module (tool_module_rule).
  • Soft file limit 250 lines, hard 400. Architecture gate enforces this.
  • Log to stderr only — never MCP protocol stdout.

6. Testing policy

Required. make test runs the full suite with coverage (60% minimum). Contract fixtures live in tests/. Capture fresh fixtures with make capture-fixtures against a live lab.

7. Security (hard stops)

  • No secrets committed. detect-secrets + gitleaks enforce.
  • Never log secrets or tokens to any output stream.
  • All write operations require destructive confirmation guard.
  • Do not regress Rancher 2.6.5 (compat floor) compatibility to chase newer 2.9.3 APIs. Capability detection is the bridge; both versions stay green.

Read the full file on GitHub · 79 lines

Changes

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.

  1. 2d ago Changed · -1 lines · -56 tokens per session f55d22f44ddf
  2. 6d ago First seen · 80 lines · 815 tokens per session scan A 8d2eab19fae2

Subscribe to this mod's changes

mcp-rancher AGENTS.md is an instructions file published in the GitHub repository rex/mcp-rancher (1 stars, last pushed 3d ago), licensed MIT. It adds 759 tokens to every session, about $0.0038 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.

DevOps and cloudai-appanthropicclaudecluster-managementk8s
Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens