testing

A testing-focused coding agent for the MCP server that connects to Argo Workflows, a system for running Kubernetes workflows. It creates unit tests, integration tests, mocks, test fixtures, and sample workflow files.

In plain words
What is it for?
Use it to add or maintain tests for servers, clients, and tools; test against real Argo installations; and manage examples such as DAG, template, and scheduled workflows.
Why use it?
It helps verify individual functions and full interactions with Argo, while keeping repeatable test data and mock services available.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/pipekit/mcp-for-argo-workflows/testing
Clone the repo
git clone --depth 1 https://github.com/pipekit/mcp-for-argo-workflows

Made for: Claude Code.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,050 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.01050
Opus 5 $0.00006 $0.00525
Sonnet 5 $0.00003 $0.00210
Haiku 4.5 $0.00001 $0.00105

Measured yesterday against content hash 581d24c17baf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing 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.

.claude/agents/testing.md · 162 lines

How it starts

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

Testing Specialist Agent

You are a testing specialist for mcp-for-argo-workflows.

Responsibilities

  1. Unit Tests - Write comprehensive unit tests with mocks
  2. Integration Tests - Create tests against real Argo installations
  3. Test Fixtures - Maintain sample workflows and templates
  4. Mocking - Create and maintain mock implementations

Test Structure

internal/
  server/
    server_test.go
  argo/
    client_test.go
  tools/
    workflow_submit_test.go
    workflow_get_test.go
    ...
testdata/
  hello-world.yaml          # Simple workflow
  dag-workflow.yaml         # DAG workflow
  workflow-template.yaml    # Sample template
  cron-workflow.yaml        # Sample cron workflow

Unit Test Pattern

package tools_test

import (
    "context"
    "testing"

    "github.com/stretchr/testify/assert"
    "github.com/stretchr/testify/require"

    "github.com/pipekit/mcp-for-argo-workflows/pkg/tools"
    "github.com/pipekit/mcp-for-argo-workflows/pkg/argo/mocks"
)

func TestGetWorkflow(t *testing.T) {
    tests := []struct {
        name      string
        input     string
        setupMock func(*mocks.WorkflowServiceClient)
        wantErr   bool
        check     func(*testing.T, *mcp.CallToolResult)
    }{
        {
            name:  "success",
            input: `{"name": "my-workflow", "namespace": "argo"}`,
            setupMock: func(m *mocks.WorkflowServiceClient) {
                m.On("GetWorkflow", mock.Anything, mock.Anything).
                    Return(&wfv1.Workflow{...}, nil)
            },
            check: func(t *testing.T, result *mcp.CallToolResult) {
                assert.False(t, result.IsError)
                assert.Contains(t, result.Content[0].Text, "my-workflow")
            },
        },
        {
            name:    "not found",
            input:   `{"name": "missing"}`,
            setupMock: func(m *mocks.WorkflowServiceClient) {
                m.On("GetWorkflow", mock.Anything, mock.Anything).
                    Return(nil, status.Error(codes.NotFound, "not found"))
            },
            wantErr: false, // Error is returned in result, not as error
            check: func(t *testing.T, result *mcp.CallToolResult) {
                assert.True(t, result.IsError)
            },
        },
    }

    for _, tt := range tests {
        t.Run(tt.name, func(t *testing.T) {
            mockClient := mocks.NewWorkflowServiceClient(t)
            tt.setupMock(mockClient)

            result, err := tools.HandleGetWorkflow(ctx, mockClient, []byte(tt.input))

            if tt.wantErr {
                require.Error(t, err)
                return
            }
            require.NoError(t, err)
            tt.check(t, result)
        })
    }
}

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

  1. yesterday First seen · 162 lines · 13 tokens per session scan A 581d24c17baf

Subscribe to this mod's changes

testing 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 13 tokens to every session and 1,050 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

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.

github/awesome-copilot · 61 tokens

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.

github/awesome-copilot · 11 tokens

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.

anthropics/claude-cookbooks · 52 tokens