Borrowing it
Nothing to install: this file belongs to joslat/maf-doctor. 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/joslat/maf-doctor/main/.github/instructions/maf-testing.instructions.mdgit clone --depth 1 https://github.com/joslat/maf-doctorWrote 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/instructions/joslat/maf-doctor/maf-testing)<a href="https://agentmods.dev/instructions/joslat/maf-doctor/maf-testing"><img src="https://agentmods.dev/badge/instructions/joslat/maf-doctor/maf-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/instructions/joslat/maf-doctor/maf-testing"><img src="https://agentmods.dev/badge/instructions/joslat/maf-doctor/maf-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.01584 | $0.01584 |
| Opus 5.5 | $0.00634 | $0.00634 |
| Sonnet 5.5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
maf-doctor maf-testing.instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAF Testing — Hermetic Patterns
When you write tests for MAF code in this repo, follow these patterns. They exist because we've been bitten by their absence — every entry has a "why" behind it.
Hard rules
- No live LLM calls in tests. Ever. Cost is one reason; flakiness, throttling, and "the prompt drifted in production but tests still passed" are the bigger ones.
- AAA structure with explicit comment markers:
// Arrange,// Act,// Assert. Three blocks, separated by a blank line. A test that needs more than 3 blocks is doing too much. - One assertion subject per test. Multiple
Assert.X(...)calls is fine when they describe one fact (e.g., "this finding has the right ID and the right line"). - Test name follows
Method_Scenario_Outcome. Example:ParseGitDiffOutput_IgnoresBinAndObjPaths_FiltersThem. - Hermetic > integration. Prefer in-memory string sources over temp dirs. Prefer temp dirs over real network. Real network needs explicit justification.
- No
Thread.Sleep, no wall-clock dependencies, no GUIDs in assertions. Each is a known source of CI flake.
The ScriptedChatClient pattern (THE canonical mock)
For any test that needs an IChatClient, never instantiate AzureOpenAIClient.AsChatClient(...). Use a scripted mock — same shape as the scaffolder generates:
private sealed class ScriptedChatClient : IChatClient
{
private readonly string _response;
public ScriptedChatClient(string response) => _response = response;
public Task<ChatResponse> GetResponseAsync(
IEnumerable<ChatMessage> messages,
ChatOptions? options = null,
CancellationToken cancellationToken = default)
=> Task.FromResult(new ChatResponse(new ChatMessage(ChatRole.Assistant, _response)));
public async IAsyncEnumerable<ChatResponseUpdate> GetStreamingResponseAsync(
IEnumerable<ChatMessage> messages,
ChatOptions? options = null,
[EnumeratorCancellation] CancellationToken cancellationToken = default)
{
yield return new ChatResponseUpdate(ChatRole.Assistant, _response);
await Task.CompletedTask;
}
public object? GetService(Type serviceType, object? serviceKey = null) => null;
public void Dispose() { }
}
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 · 138 lines · 1,584 tokens per session scan A b85b502a6dfc
maf-doctor maf-testing.instructions.md is an instructions file published in the GitHub repository joslat/maf-doctor (14 stars, last pushed 5d ago), licensed MIT. It adds 1,584 tokens to every session, about $0.0063 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 instructions, from other repositories
plan-forge powershell.instructions.md
PowerShell best practices for Azure IaC — Az module, script structure, Pester testing, PSScriptAnalyzer.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.