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/pipekit/mcp-for-argo-workflows/claude-mdgit clone --depth 1 https://github.com/pipekit/mcp-for-argo-workflowsWrote 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/pipekit/mcp-for-argo-workflows/claude-md)<a href="https://agentmods.dev/instructions/pipekit/mcp-for-argo-workflows/claude-md"><img src="https://agentmods.dev/badge/instructions/pipekit/mcp-for-argo-workflows/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.01490 | $0.01490 |
| Opus 5 | $0.00745 | $0.00745 |
| Sonnet 5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
mcp-for-argo-workflows 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 3d 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 — 142 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.
Project Overview
MCP (Model Context Protocol) server for Argo Workflows, allowing AI assistants like Claude to interact with Argo Workflows via standardized tools.
Repository: github.com/pipekit/mcp-for-argo-workflows
Goals
- Standalone Go binary using the official MCP Go SDK
- Support stdio, streamable HTTP and HTTP/SSE transports
- Support both direct Kubernetes API access and Argo Server connections
- Cover all major CLI operations as MCP tools
Key Dependencies
github.com/modelcontextprotocol/go-sdk— Official MCP Go SDKgithub.com/argoproj/argo-workflows/v3/pkg/apiclient— Argo client libraries
Build Commands
make all # Run fmt, vet, lint, test and build the linux/amd64 binary
make build-all # Cross-compile binaries for all platforms into dist/
make test # Run tests with race detection and coverage
make lint # Run golangci-lint
make lint-fix # Run golangci-lint with auto-fix
make fmt # Run gofmt and goimports
make vet # Run go vet
make clean # Remove build artifacts
Binaries land in dist/ (e.g. dist/mcp-for-argo-workflows-linux-amd64). Run make help to see all targets.
Directory Structure
cmd/mcp-for-argo-workflows/ # main.go entry point
pkg/ # Reusable packages — importable by other MCP servers
argo/ # Argo client wrapper
tools/ # MCP tool implementations
prompts/ # MCP prompt implementations
resources/ # MCP resource implementations (embedded docs)
internal/ # Binary-specific glue (not importable externally)
server/ # MCP server wiring
config/ # CLI flag / env parsing
version/ # Build-time version info
Architecture
Connection Modes
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.
- 3d ago First seen · 142 lines · 1,490 tokens per session scan A 0c417a955392
mcp-for-argo-workflows CLAUDE.md is an instructions file published in the GitHub repository pipekit/mcp-for-argo-workflows (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,490 tokens to every session, about $0.0075 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
AppClaw CLAUDE.md
Claude Code instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).
awsmux AGENTS.md
Instructions for 0hardik1/awsmux, covering agents.md, what awsmux is, build, test, verify, layout and the safety model — invariants you must not weaken.
gcnv-mcp-server AGENTS.md
Instructions for NetApp/gcnv-mcp-server, covering assistant briefing, non-negotiable code policy, session startup — ontap audit logging (must do), userintent parameter (when audit logging is enabled) and operating principles.
google-connector AGENTS.md
Instructions for kevinbkt10/google-connector, covering agents.md — google connector, objetivo do usuário, regras, fluxo em um pedido (“um clique” com a ia) and instalação (comandos).
EpesiCRM CLAUDE.md
Claude Code instructions for jtylek/EpesiCRM, covering claude.md, project, environment quirks (this machine), commands and architecture.
cron-mcp CLAUDE.md
Claude Code instructions for Shreyas-Profile/cron-mcp, covering deploying cron-mcp to hetzner + regiq.in, server (shared with the rest of the globalion mcp fleet), deploy a new version, first-time subdomain wiring (cron.regiq.in) and env vars.