Borrowing it
Nothing to install: this file belongs to future-architect/uzomuzo-oss. 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/future-architect/uzomuzo-oss/main/.github/instructions/test-design.instructions.mdgit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWrote 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/future-architect/uzomuzo-oss/test-design)<a href="https://agentmods.dev/instructions/future-architect/uzomuzo-oss/test-design"><img src="https://agentmods.dev/badge/instructions/future-architect/uzomuzo-oss/test-design/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/future-architect/uzomuzo-oss/test-design"><img src="https://agentmods.dev/badge/instructions/future-architect/uzomuzo-oss/test-design.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.02504 | $0.02504 |
| Opus 5.5 | $0.01002 | $0.01002 |
| Sonnet 5.5 | $0.00501 | $0.00501 |
| Haiku 4.5 | $0.00250 | $0.00250 |
Grade A, and why
uzomuzo-oss test-design.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 8d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Design — pre-PR lens
A rule for what to test. The companion rule testing-performance.md covers
how to write Go tests (t.Parallel, t.Cleanup, fixture layout, race detection,
benchmark hygiene). Post-PR review patterns that were actually caught land in
copilot-learned-coding.md. This document is the pre-PR lens that prevents the
"what cases did I forget?" gap before code review starts.
When to consult
- A planner or architect drafting a test plan for a new feature
- An implementer writing a new function / service / infrastructure client
- A code reviewer asking "is edge-case coverage sufficient?" / "is there a fuzz target missing for this parser?"
Cross-layer rule
Tests respect the same layer rules as production code. Under DDD,
internal/domain/** tests must not import internal/infrastructure/** or
third-party modules that infrastructure depends on. Domain tests stay
pure-Go + stdlib + your own domain types. Application-layer tests may compose
mocks of infrastructure interfaces but must not import concrete infrastructure
clients (depsdev, GitHub, nuget, pypi, etc.) directly.
When property-based testing (pgregory.net/rapid) is adopted in the future, do
not put rapid imports directly under internal/domain/**. Use an isolated
package (e.g. internal/propertytests/<layer>/) gated by a build tag
(//go:build pbt) so production code remains dep-free.
Input-selection techniques (classical QA)
Each technique gets a 1-2 line definition and a concrete pin in this repo. The pins are existing tests — the point here is to show what each technique looks like in this codebase, not to introduce new tests.
Equivalence Partitioning
Divide the input domain into classes that should behave identically; test one representative per class. The point is not coverage by line count but coverage by behavior class — three inputs in the same class do not add information.
- Repo pin:
internal/common/purl/parser.go::ParsePURLandinternal/common/purl/parser_test.go. Input domain partitions by PURL shape: known ecosystem with namespace (Maven), known ecosystem without namespace (Go, npm flat), known ecosystem with version qualifier, malformed string, empty string. One representative per class.
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.
- 8d ago Changed · +1 lines · +14 tokens per session 4b99e558cec3
- 1mo ago First seen · 218 lines · 2,490 tokens per session scan A 555a46030fd9
uzomuzo-oss test-design.instructions.md is an instructions file published in the GitHub repository future-architect/uzomuzo-oss (42 stars, last pushed today), licensed Apache-2.0. It adds 2,504 tokens to every session, about $0.0100 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-09-01.
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.
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.
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).