Borrowing it
Nothing to install: this file belongs to mrlarson2007/copilot-tdd-harness. 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/mrlarson2007/copilot-tdd-harness/master/.github/instructions/tdd-patterns.instructions.mdgit clone --depth 1 https://github.com/mrlarson2007/copilot-tdd-harnessWrote 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/mrlarson2007/copilot-tdd-harness/tdd-patterns)<a href="https://agentmods.dev/instructions/mrlarson2007/copilot-tdd-harness/tdd-patterns"><img src="https://agentmods.dev/badge/instructions/mrlarson2007/copilot-tdd-harness/tdd-patterns/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/mrlarson2007/copilot-tdd-harness/tdd-patterns"><img src="https://agentmods.dev/badge/instructions/mrlarson2007/copilot-tdd-harness/tdd-patterns.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.00385 | $0.00385 |
| Opus 5.5 | $0.00154 | $0.00154 |
| Sonnet 5.5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
copilot-tdd-harness tdd-patterns.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.
What it actually says
Go TDD Patterns
Treat this file as the project-specific source of truth for TDD work in this repository.
Commands
- For Go changes under
samples/fizzbuzz-go, rungo test ./...from that directory. - Run
go build ./...fromsamples/fizzbuzz-goonly when a build verification step is warranted. - There is no root Go module for this repository.
Run the narrowest practical command first when validating a small change, but fall back to the configured full test command before ending substantial work.
File Layout
- Source files are Go files under the repository using
*.go. - Tests are package-local files named
*_test.go. - Prefer adding tests next to the production code they exercise.
Test Naming
- Name tests with the Go
Test...prefix. - Use the repository convention
TestWhenCondition_ShouldExpectedOutcome. - Keep each new TDD cycle to exactly one new test covering exactly one behavior.
Examples:
TestWhenModeIsUnsupported_ShouldReturnErrorModeTestWhenTestsFail_ShouldBlock
Assertions
- Use the Go standard library
testingpackage. - Prefer
t.Fatalfort.Fatalwith explicit expected/actual output. - Keep assertion messages concrete and behavior-focused.
Stand-ins
- Prefer handwritten fakes or stubs behind small interfaces.
- Use standard library testing tools unless a strong reason exists to add a mock framework.
- Keep stand-ins local to the test package unless they are broadly reusable.
Repository Notes
- This repo now contains packaged harness assets plus sample Go code under
samples/fizzbuzz-go. - Validate Go changes in the owning sample module rather than from the repository root.
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 · 50 lines · 385 tokens per session scan A fc1ac0faafe7
copilot-tdd-harness tdd-patterns.instructions.md is an instructions file published in the GitHub repository mrlarson2007/copilot-tdd-harness (5 stars, last pushed 2d ago), licensed MIT. It adds 385 tokens to every session, about $0.0015 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-31.
Other instructions, from other repositories
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.