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/sanjaypsachdev/mcp-server-openshift/claude-mdgit clone --depth 1 https://github.com/sanjaypsachdev/mcp-server-openshiftWhat 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.01022 | $0.01022 |
| Opus 5 | $0.00511 | $0.00511 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
mcp-server-openshift 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 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 — 80 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.
Commands
# Build
npm run build # tsc compile to dist/
# Development (no compile step)
npm run dev # tsx src/index.ts (stdio)
npm run dev:http # tsx src/index.ts --http (SSE on :3000)
# Run the server
npm run start # dist/index.js (stdio, default)
npm run start:sse # dist/index.js --sse --port=3000
# Test
npm test # vitest (run once)
npm run test:watch # vitest --watch
npm run test:coverage # vitest --coverage (requires ≥80% on all metrics)
# Single test file
npx vitest run tests/oc-login.test.ts
# Lint
npm run lint # eslint src/
npm run lint:fix # eslint src/ --fix
Architecture
MCP server structure
src/index.ts is the single entry point. It creates OpenShiftMCPServer, which wires together all four MCP capability types:
- Tools — 14
oc_*tools registered inindex.ts, each insrc/tools/oc-*.ts - Resources — 3 static read-only resources in
src/resources/openshift://cluster-info,openshift://project-list,openshift://app-templates
- Prompts — 2 prompt templates in
src/prompts/ - Sampling — pod-log sampling handler in
src/sampling/pod-logs.ts
Transport is auto-detected: stdio by default; HTTP/SSE when --http, --sse, --port=N, or MCP_TRANSPORT=sse/http is set.
Runtime environment variables: OPENSHIFT_CONTEXT, OPENSHIFT_NAMESPACE (cluster defaults), MCP_TRANSPORT, MCP_PORT, MCP_HOST (server config).
Note: src/tools/oc-status.ts exists as a reference implementation showing the full tool utility pattern but is intentionally not registered in index.ts.
Tool pattern
Every tool file exports two things:
- A
Toolobject (the MCP tool definition withname,description,inputSchema) - A
handle*async function that takes typed args and returns an MCPcontentresponse
Input validation uses Zod schemas defined in src/models/tool-models.ts. All schemas and their inferred TypeScript types live there; individual tool files import from it. OcRolloutSchema and OcStartBuildSchema are defined there but have no corresponding tool files yet — stubs for planned tools.
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 · 80 lines · 1,022 tokens per session scan A e3e62f0c7c5d
mcp-server-openshift CLAUDE.md is an instructions file published in the GitHub repository sanjaypsachdev/mcp-server-openshift (1 stars, last pushed 2mo ago), licensed MIT. It adds 1,022 tokens to every session, about $0.0051 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
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.