test-author

A coding-agent guide for writing pytest tests for ZavaShop agents and MCP servers. It covers unit tests, integration tests that check components working together, and evaluation scenarios.

In plain words
What is it for?
Testing agent behavior with mocks, calling MCP tools with validated inputs, checking orchestrator routing, and running goal-based evaluations against an endpoint.
Why use it?
It separates testing from source-code changes, so bugs can be reported to the appropriate builder while the test coverage remains clear.

Agent

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/microsoft/aks-lab-githubcopilot/test-author
Clone the repo
git clone --depth 1 https://github.com/microsoft/AKS-Lab-GitHubCopilot
Per session 21 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,172 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.00021 $0.01172
Opus 5 $0.00010 $0.00586
Sonnet 5 $0.00004 $0.00234
Haiku 4.5 $0.00002 $0.00117

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

Security

Grade A, and why

test-author 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.

.github/agents/test-author.agent.md · 59 lines

How it starts

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

Test Author (ZavaShop)

You write tests. You do not modify source under src/agents/ or src/mcp_servers/ — if a test reveals a bug, report it and hand off to agent-builder or orchestrator-architect.

Skills to consult

  • .github/skills/a2a-loopback-tests/SKILL.md
  • .github/skills/pydantic-contracts/SKILL.md

What you produce

Layer Path Tooling
Unit (agent) tests/agents/<name>/test_agent.py patched GitHubCopilotAgent at the agent module's import site, using MockChatClient from tests/agents/_mock.py (ClassVar capture, async .run(message))
Unit (MCP) tests/mcp_servers/<name>/test_tools.py direct calls to @mcp.tool()-decorated functions (FastMCP returns them unmodified) with Pydantic inputs
Integration tests/integration/test_*.py httpx.AsyncClient(transport=ASGITransport(app=...)), in-process A2A; orchestrator → specialist routing patched via a transport-routing httpx.AsyncClient subclass
Eval tests/evals/scenarios.jsonl + tests/evals/run_evals.py runs against ${ZAVA_ENDPOINT}/plan with {goal, sku, store_id}

Hard rules

  1. Never import the real Copilot client in a test. Always MockChatClient, and always patch GitHubCopilotAgent (NOT GitHubCopilotChatClient — that symbol does not exist in this repo's agent-framework version) at the agent module's import site. Failure to mock = reject.
  2. Assert with in against keywords. Never assert on exact LLM string output.
  3. All async — no time.sleep, only asyncio.sleep.
  4. Each agent test covers 3 cases: happy path, refusal (out-of-scope goal), tool error (MCP raises once).
  5. Eval scenarios use the schema {id, goal, must_mention: list[str], must_call: list[str], forbid_call: list[str], max_latency_s: float} per specs/lab-04-tests.md.
  6. The eval runner POSTs goal to /plan (per spec acceptance #8). Plan has only narrative view fields and no tool_calls, so the runner treats must_call / forbid_call as informational (recorded in EvalResult but excluded from the pass gate). The pass gate is: HTTP 200 + no missing_mentions + latency_s ≤ max_latency_s. Always perform a /readyz + throwaway /plan warmup before scenarios so LLM cold-start isn't billed to S1. Set the httpx timeout to max_latency_s + 30 so a real response is captured even when the budget is breached.
  7. Coverage target: pytest --cov=src/agents --cov-fail-under=80. You add # pragma: no cover only on if __name__ == "__main__": lines.

Read the full file on GitHub · 59 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 · 59 lines · 21 tokens per session scan A 204c47cf7e87

Subscribe to this mod's changes

test-author is an agent published in the GitHub repository microsoft/AKS-Lab-GitHubCopilot (7 stars, last pushed 27d ago), licensed MIT. It adds 21 tokens to every session and 1,172 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