What is mcaf-testing?

A workflow for adding or updating automated tests according to a repository’s AGENTS.md instructions. It covers feature work, bug fixes, refactoring, and regression tests.

Use it to create tests for new behavior, reproduce and guard against bugs, protect refactors, and choose suitable integration, API, or user-interface coverage.

It helps verify changed behavior at the right scope and reduces the chance that a fix or refactor introduces a new failure.

mcaf-testing — Skill by managedcode

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 skills/managedcode/mcpgateway/mcaf-testing

Any agent

npx skills add managedcode/MCPGateway --skill mcaf-testing

Clone the repo

git clone --depth 1 https://github.com/managedcode/MCPGateway

Made for: Claude Code, Codex.

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 0 findings. Scan, not verified.

Origin 91% copy Near-identical to another mod 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	$0.00056	$0.01032
Opus 5	$0.00028	$0.00516
Sonnet 5	$0.00011	$0.00206
Haiku 4.5	$0.00006	$0.00103

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

Security

Grade A, and why

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

Origin

This is a copy

91% identical to mcaf-testing — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.codex/skills/mcaf-testing/SKILL.md · 110 lines

How it starts

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

MCAF: Testing

Trigger On

implementing a feature or bugfix
adding a regression test for a failure
protecting a refactor with automated verification

Value

produce a concrete project delta: code, docs, config, tests, CI, or review artifact
reduce ambiguity through explicit planning, verification, and final validation skills
leave reusable project context so future tasks are faster and safer

Do Not Use For

repo-wide delivery policy with no test change
documentation-only changes unless they alter executable verification

Inputs

the nearest AGENTS.md
the changed behaviour and touched boundaries
existing tests near the impacted code path

Quick Start

Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

Read the repo’s real verification commands from AGENTS.md.
Start with a failing test first when the change adds behaviour or fixes a bug.
Start with the smallest meaningful test scope:
- new or changed tests
- related suite
- broader regressions
When the stack is .NET, use mcaf-dotnet as the orchestration skill when the task spans code, tests, and verification, and route framework mechanics through exactly one matching skill:
- mcaf-dotnet-xunit
- mcaf-dotnet-tunit
- mcaf-dotnet-mstest
Prefer integration, API, or UI coverage when behaviour crosses boundaries.
Prove the user flow or caller-visible system flow, not just internal details.
Add a regression test for every bug that can be captured reliably.
If the stack is .NET and production code changed, do not stop at tests only. Finish with the repo-defined format and analyzer pass as well.
Use deeper testing references only when the repo’s current strategy is unclear.

Deliver

automated tests close to the changed behaviour
verification results that match the repo’s real commands

Read the full file on GitHub · 110 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

yesterday First seen · 110 lines · 56 tokens per session scan A d1afce879ae3

Subscribe to this mod's changes

mcaf-testing is a skill published in the GitHub repository managedcode/MCPGateway (5 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,032 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to mcaf-testing, differing in 27 lines, and is treated as a copy.

Debugging Frontend Testing ai-extensions csharp dotnet embeddings mcp mcp-gateway

mcaf-testing