docs-ssot: Instructions file for GitHub Copilot

.github/instructions/go-test.instructions.md

docs-ssot go-test.instructions.md is an instructions file for GitHub Copilot from hiromaily/docs-ssot. It costs 1,660 tokens per session, scanned A, original, MIT.

A set of rules for writing Go tests in a specific codebase. It covers package choices, parallel tests, table-driven tests, and subtest names.

In plain words
What is it for?
Use it while adding or reviewing Go tests, especially tests in the mcp-server directory. It explains when to use internal or external test packages and when not to run tests in parallel.
Why use it?
It prevents inconsistent test structure and helps tests meet the project's linting and concurrency requirements.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is hiromaily/docs-ssot's own configuration. It tells GitHub Copilot how to work on docs-ssot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything docs-ssot configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hiromaily/docs-ssot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hiromaily/docs-ssot/main/.github/instructions/go-test.instructions.md
Clone the repo
git clone --depth 1 https://github.com/hiromaily/docs-ssot

Made for: GitHub Copilot.

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

agentmods badge for docs-ssot go-test.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hiromaily/docs-ssot/go-test/github.svg)](https://agentmods.dev/instructions/hiromaily/docs-ssot/go-test)
Your own site
<a href="https://agentmods.dev/instructions/hiromaily/docs-ssot/go-test"><img src="https://agentmods.dev/badge/instructions/hiromaily/docs-ssot/go-test/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.

agentmods 80×15 button for docs-ssot go-test.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hiromaily/docs-ssot/go-test"><img src="https://agentmods.dev/badge/instructions/hiromaily/docs-ssot/go-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,660 This file is loaded in full into every session.
When invoked 1,660 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01660 $0.01660
Opus 5.5 $0.00664 $0.00664
Sonnet 5.5 $0.00332 $0.00332
Haiku 4.5 $0.00166 $0.00166

Measured 1mo ago against content hash c87672d2205e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs-ssot go-test.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.

.github/instructions/go-test.instructions.md · 193 lines

How it starts

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

Go Test Rules

These rules apply to all *_test.go files in mcp-server/. Read them before writing any test.

Package declaration

Choose based on whether the test needs unexported symbols:

  • Same package (package orchestrator): when the test needs access to unexported types, functions, or variables. Used in orchestrator/ and other pure-logic packages.
  • External package (package state_test): when tests should only touch the exported API. Used in state/ and tools/ to keep tests honest about the public surface.

Do not mix both styles in the same directory.

Parallelism

Every test function and every t.Run subtest must call t.Parallel() as its first statement. This is enforced by the tparallel linter.

func TestFoo(t *testing.T) {
    t.Parallel()

    t.Run("case", func(t *testing.T) {
        t.Parallel() // required inside every t.Run subtest
        ...
    })
}

Exception: tests that mutate OS-level global state (environment variables, working directory) must NOT call t.Parallel(). Add a comment explaining why.

In Go 1.22+, the loop variable in for _, tc := range tests is scoped per iteration — tc := tc capture workarounds are not needed and must not be added.

Table-driven tests

Use table-driven tests with t.Run when two or more cases share the same function signature and assertion pattern. Do not write individual TestFoo_CaseA, TestFoo_CaseB functions for structurally identical cases — merge them into one table.

tests := []struct {
    name  string
    input string
    want  string
}{
    {name: "foo", input: "a", want: "b"},
    {name: "bar", input: "c", want: "d"},
}
for _, tc := range tests {
    t.Run(tc.name, func(t *testing.T) {
        t.Parallel()
        got := fn(tc.input)
        if got != tc.want {
            t.Errorf("fn(%q) = %q, want %q", tc.input, got, tc.want)
        }
    })
}

For 2D matrix tests (e.g. sourceType × effort), use tc.sourceType+"/"+tc.effort as the subtest name — the / creates a hierarchy that makes -run filtering precise.

Read the full file on GitHub · 193 lines

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.

  1. 1mo ago First seen · 193 lines · 1,660 tokens per session scan A c87672d2205e

Subscribe to this mod's changes

docs-ssot go-test.instructions.md is an instructions file published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,660 tokens to every session, about $0.0066 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.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens