Borrowing it
Nothing to install: this file belongs to managedcode/PrompterOne. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/managedcode/PrompterOne/main/.codex/skills/mcaf-testing/SKILL.mdgit clone --depth 1 https://github.com/managedcode/PrompterOneWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/managedcode/prompterone/mcaf-testing)<a href="https://agentmods.dev/skills/managedcode/prompterone/mcaf-testing"><img src="https://agentmods.dev/badge/skills/managedcode/prompterone/mcaf-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/managedcode/prompterone/mcaf-testing"><img src="https://agentmods.dev/badge/skills/managedcode/prompterone/mcaf-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00056 | $0.01130 |
| Opus 5.5 | $0.00022 | $0.00452 |
| Sonnet 5.5 | $0.00011 | $0.00226 |
| Haiku 4.5 | $0.00006 | $0.00113 |
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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- mcaf-testing — 95% identical, 6 lines differ
- mcaf-testing — 91% identical, 27 lines differ
How it starts
The opening of the file, as written. The whole thing — 113 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.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith 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 the external
.NETskills from the Managed Code Skills catalog, usemcaf-dotnetas the orchestration skill when the task spans code, tests, and verification, and route framework mechanics through exactly one matching skill:mcaf-dotnet-xunitmcaf-dotnet-tunitmcaf-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.
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.
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.
- 1mo ago First seen · 113 lines · 56 tokens per session scan A ea0e390d617d
mcaf-testing is a skill published in the GitHub repository managedcode/PrompterOne (45 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,130 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
mcp-harness
Use this harness to validate Agentweaver's MCP protocol surface, capture the complete tools/call request/response evidence, and emit a normalized agentweaver.persona-judge-verdict/v1 JSON verdict. It is for MCP end-to-end validation, MCP tool-contract regression checks, and investigation of an MCP-reported issue; use…
bug-fix
Guided end-to-end bug-fix workflow for Plan Forge tempering bugs — load → pre-fix review → write failing test → fix → validate → post-fix sweep → close. Composes /code-review, /clean-code-review, /forge-quench, and /test-sweep around the forgebug tool surface so a fix never closes without a regression check.
audit-loop
Run a recursive audit drain loop — discover findings from the running system, triage each into bug/spec/classifier lanes, repeat until convergence. USE FOR: end-to-end audit of a deployed or locally-running app, draining findings to zero. DO NOT USE FOR: single-shot tempering runs (use forgetemperingrun), one-off bug…
cratis-engineering-regression-cluster
Stop fixing instances when one surface keeps breaking - name the failure class, add the gate that owns it, prove the gate fails, then fix the instance. Use when a third bug, regression, revert or review finding lands on the same screen, endpoint, command, workflow or module, when the same kind of fix keeps being…
test-strategy-reproduction
Turn reported behavior into reliable repros, risk-based tests, and clear acceptance evidence.
risk-based-testing-with-code-health
Use when a user asks what to test first based on CodeScene findings, especially for high-risk hotspots or pull-request change sets. Only in repositories that opted into the cratis/codescene profile and have CodeScene MCP tools available; otherwise do not use.