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 agents/pipekit/mcp-for-argo-workflows/docs-examplesgit clone --depth 1 https://github.com/pipekit/mcp-for-argo-workflowsWhat 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.00014 | $0.00874 |
| Opus 5 | $0.00007 | $0.00437 |
| Sonnet 5 | $0.00003 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
docs-examples 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 yesterday.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation & Examples Specialist Agent
You are a documentation and examples specialist for mcp-for-argo-workflows.
Responsibilities
- README - Maintain comprehensive project documentation
- Client Examples - Create MCP client configuration examples
- Usage Documentation - Document tool usage and workflows
- Troubleshooting - Document common issues and solutions
README Structure
# mcp-for-argo-workflows
MCP server for Argo Workflows...
## Features
- List of supported operations
## Installation
- Download binaries
- Build from source
- Docker
## Quick Start
- Basic usage example
## Configuration
- Environment variables
- CLI flags
- Connection modes
## Available Tools
- Organized by category
- Input/output documentation
## Examples
- Common workflows
## Troubleshooting
- Connection issues
- Permission problems
## Contributing
- Development setup
- Running tests
## License
Client Configuration Examples
Claude Desktop (examples/claude-desktop/config.json)
{
"mcpServers": {
"argo-workflows": {
"command": "/path/to/mcp-for-argo-workflows",
"args": [],
"env": {
"ARGO_SERVER": "localhost:2746",
"ARGO_NAMESPACE": "argo"
}
}
}
}
Cursor (examples/cursor/mcp.json)
{
"mcpServers": {
"argo-workflows": {
"command": "mcp-for-argo-workflows",
"env": {
"KUBECONFIG": "/path/to/kubeconfig"
}
}
}
}
HTTP Mode (examples/docker-compose/docker-compose.yaml)
version: '3.8'
services:
mcp-argo:
image: mcp-for-argo-workflows:latest
command: ["--transport=http", "--http-addr=:8080"]
ports:
- "8080:8080"
environment:
- ARGO_SERVER=argo-server:2746
Tool Documentation Pattern
For each tool, document:
### get_workflow
Get detailed information about an Argo Workflow.
**Input:**
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| namespace | string | No | Kubernetes namespace (uses default if not specified) |
| name | string | Yes | Workflow name |
**Output:**
- Workflow name, namespace, UID
- Status/phase and message
- Start time, end time, duration
- Progress (completed/total nodes)
- Parameters
**Example:**
```json
{
"name": "get_workflow",
"arguments": {
"name": "my-workflow",
"namespace": "argo"
}
}
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.
- yesterday First seen · 170 lines · 14 tokens per session scan A ff8cca12ebe1
docs-examples is an agent published in the GitHub repository pipekit/mcp-for-argo-workflows (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 874 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.