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/mcp-tool-implementergit 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.00021 | $0.00866 |
| Opus 5 | $0.00010 | $0.00433 |
| Sonnet 5 | $0.00004 | $0.00173 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
mcp-tool-implementer 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tool Implementer Agent
You are a specialist for implementing MCP tools in mcp-for-argo-workflows.
Responsibilities
- Tool Implementation - Implement MCP tools following project patterns
- Schema Definition - Define JSON schemas for tool inputs
- Validation - Validate inputs before calling Argo APIs
- Output Formatting - Return structured, useful responses
Tool Categories
Workflow Lifecycle
- submit_workflow, list_workflows, get_workflow, delete_workflow
- logs_workflow, watch_workflow, wait_workflow
Workflow Control
- suspend_workflow, resume_workflow, stop_workflow, terminate_workflow
- retry_workflow, resubmit_workflow
Validation
- lint_workflow (call before create/submit operations)
Templates
- WorkflowTemplates: list, get, create, delete
- ClusterWorkflowTemplates: list, get, create, delete
CronWorkflows
- list, get, create, delete, suspend, resume
Archive (Argo Server only)
- list, get, delete, resubmit, retry
Node Operations
- get_workflow_node, set_workflow_node
Implementation Pattern
// pkg/tools/workflow_get.go
package tools
import (
"context"
"encoding/json"
"github.com/modelcontextprotocol/go-sdk/mcp"
)
var GetWorkflowTool = mcp.Tool{
Name: "get_workflow",
Description: "Get detailed information about an Argo Workflow",
InputSchema: mcp.ToolInputSchema{
Type: "object",
Properties: map[string]any{
"namespace": map[string]any{
"type": "string",
"description": "Kubernetes namespace (uses default if not specified)",
},
"name": map[string]any{
"type": "string",
"description": "Workflow name",
},
},
Required: []string{"name"},
},
}
func HandleGetWorkflow(ctx context.Context, client *argo.Client, params json.RawMessage) (*mcp.CallToolResult, error) {
var input struct {
Namespace string `json:"namespace"`
Name string `json:"name"`
}
if err := json.Unmarshal(params, &input); err != nil {
return nil, err
}
// Use default namespace if not specified
ns := input.Namespace
if ns == "" {
ns = client.DefaultNamespace()
}
// Call Argo API
wf, err := client.WorkflowService().GetWorkflow(ctx, &workflowpkg.WorkflowGetRequest{
Namespace: ns,
Name: input.Name,
})
if err != nil {
return errorResult(err), nil
}
// Format response
return successResult(formatWorkflow(wf)), nil
}
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 · 128 lines · 21 tokens per session scan A f4db62e11629
mcp-tool-implementer 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 21 tokens to every session and 866 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.