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/kubeflow/mcp-server/agents-mdgit clone --depth 1 https://github.com/kubeflow/mcp-serverWhat 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.02113 | $0.02113 |
| Opus 5 | $0.01056 | $0.01056 |
| Sonnet 5 | $0.00423 | $0.00423 |
| Haiku 4.5 | $0.00211 | $0.00211 |
Grade A, and why
mcp-server 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.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Who This Is For
- AI agents: Automate repository tasks with minimal context
- Contributors: Humans using AI assistants or working directly
- Maintainers: Ensure assistants follow project conventions and CI rules
Agent Behavior Policy
AI agents should:
- Make atomic, minimal, and reversible changes.
- Prefer local analysis (
uv run,make verify,make test-python) before proposing commits. - NEVER modify configuration, CI/CD, or release automation unless explicitly requested.
- Avoid non-deterministic code or random seeds without fixtures.
- Use
AGENTS.mdandMakefileas the source of truth for development commands.
Agents must NOT:
- Bypass tests or linters
- Introduce dependencies without updating
pyproject.toml - Generate or commit large autogenerated files
- Change MCP tool schemas, names, or required parameters without KEP / maintainer discussion
Context Awareness
Before writing code, agents should:
- Read docstrings and existing test cases for pattern alignment
- Match import patterns from neighboring files
- Preserve existing logging, audit wrapping, and error-handling conventions
Repository Map
.github/ # GitHub Actions (CI, issue/PR templates)
docs/ # Architecture assets and diagrams
tests/ # Integration, e2e, conformance suites; shared test helpers
kubeflow_mcp/ # Main Python package (unit tests co-located as *_test.py)
├── cli.py # Click CLI entry (`kubeflow-mcp serve`)
├── __main__.py # python -m kubeflow_mcp
├── common/ # Shared constants, types, and utils
├── core/ # MCP server runtime
│ ├── server.py # FastMCP factory, client loading, tool wrapping
│ ├── auth.py # Bearer / JWT auth for HTTP
│ ├── policy.py # Personas and policy YAML filtering
│ ├── security.py # Input validation, masking, namespace checks
│ ├── resilience.py # Rate limiter and circuit breaker
│ ├── dynamic_tools.py # full / progressive / semantic tool modes
│ ├── health.py # health_check, get_server_logs
│ ├── telemetry.py # Optional OpenTelemetry tracing
│ ├── middleware.py # Audit identity ContextVars
│ ├── config.py # Config precedence (CLI > env > file)
│ ├── logging.py # Structured logging
│ └── resources.py # MCP resource registration
├── trainer/ # Trainer client (implemented)
│ ├── api/ # Tools by phase (planning, discovery, …)
│ ├── constants/ # Trainer constants
│ ├── types/ # Trainer types
│ └── resources/ # Markdown guidance for agents
├── optimizer/ # Optimizer client (stub)
└── hub/ # Hub / Model Registry client (stub)
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.
- 2d ago First seen · 216 lines · 2,113 tokens per session scan A daa3b5fc964d
mcp-server AGENTS.md is an instructions file published in the GitHub repository kubeflow/mcp-server (41 stars, last pushed 7d ago), licensed Apache-2.0. It adds 2,113 tokens to every session, about $0.0106 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
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.
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).
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.