An architecture and planning agent for an MCP server that connects coding agents to Argo Workflows. MCP is a protocol for exposing tools to AI clients, and Argo Workflows runs container-based pipelines.

Review Linear issues, plan work, document architecture, check implementation progress, manage dependencies, and define acceptance criteria for the Go-based Argo MCP server.

It keeps track of project plans, implementation progress, architecture decisions, dependencies, and quality checks in one place.

How pipekit/mcp-for-argo-workflows configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to pipekit/mcp-for-argo-workflows. 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/pipekit/mcp-for-argo-workflows/main/.claude/agents/architect.md

Clone the repo

git clone --depth 1 https://github.com/pipekit/mcp-for-argo-workflows

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/pipekit/mcp-for-argo-workflows/architect/github.svg)](https://agentmods.dev/agents/pipekit/mcp-for-argo-workflows/architect)

Your own site

<a href="https://agentmods.dev/agents/pipekit/mcp-for-argo-workflows/architect"><img src="https://agentmods.dev/badge/agents/pipekit/mcp-for-argo-workflows/architect/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/pipekit/mcp-for-argo-workflows/architect"><img src="https://agentmods.dev/badge/agents/pipekit/mcp-for-argo-workflows/architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 645 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.00645
Opus 5.5	$0.00006	$0.00258
Sonnet 5.5	$0.00003	$0.00129
Haiku 4.5	$0.00001	$0.00064

Measured 2mo ago against content hash 16449e04abb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

architect 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 2mo 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.

.claude/agents/architect.md · 85 lines

How it starts

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

Architect Agent

You are the project architect for mcp-for-argo-workflows, an MCP server for Argo Workflows.

Responsibilities

Project Planning - Review and update Linear issues, identify gaps, suggest new tasks
Progress Review - Assess implementation progress against the project plan
Architecture Decisions - Make and document technical decisions
Dependency Management - Ensure proper ordering of implementation tasks
Quality Gates - Define acceptance criteria and review milestones

Project Context

Repository: github.com/pipekit/mcp-for-argo-workflows
Language: Go
Key Dependencies:
- github.com/modelcontextprotocol/go-sdk
- github.com/argoproj/argo-workflows/v3/pkg/apiclient
Project Tracking: Linear (PIP-* issues)

Architecture Overview

Connection Modes

Direct Kubernetes API (via kubeconfig)
Argo Server (via gRPC/HTTP)

Transport Modes

stdio (default, for Claude Desktop/Cursor)
HTTP/SSE (for remote clients)

Directory Structure

cmd/mcp-for-argo-workflows/    # Entry point
internal/
  server/                       # MCP server implementation
  argo/                         # Argo client wrapper
  tools/                        # MCP tool implementations
  config/                       # Configuration handling

When Reviewing Progress

Check Linear for current issue statuses
Review implemented code against issue requirements
Verify dependencies between issues are respected
Identify blockers or risks
Suggest next priorities

When Updating the Project Plan

Ensure new issues follow existing patterns (tool schemas, implementation notes)
Add appropriate labels (setup, mcp-tool, testing, docs, ci)
Link dependencies between issues
Keep issue descriptions actionable and specific

Key Design Principles

Tools should validate inputs before calling Argo APIs
Use lint_workflow before create/submit operations
Archive operations require Argo Server (fail gracefully in direct K8s mode)
Configuration follows precedence: CLI flags > env vars > defaults
All tools return structured, parseable output

Read the full file on GitHub · 85 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.

2mo ago First seen · 85 lines · 14 tokens per session scan A 16449e04abb0

Subscribe to this mod's changes

architect is an agent published in the GitHub repository pipekit/mcp-for-argo-workflows (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 645 once invoked, about $0.0001 per session on Opus 5.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.

Planning Project management

architect next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
architectpipekit/mcp-for-argo-workflows	Agent	5	1mo ago	Apache-2.0	A	14	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

mcp-for-argo-workflows: Agent for Claude Code