copilot-kit testing.instructions.md

A set of software testing standards covering test structure, test levels, naming, test targets, and mocking.

In plain words
What is it for?
Use it when creating unit, integration, or end-to-end tests, following the Arrange-Act-Assert pattern and testing business logic, edge cases, and errors.
Why use it?
It helps teams write tests that check user-visible behavior and important logic without depending on implementation details or outside systems.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/ivanshtokov/copilot-kit/testing
Clone the repo
git clone --depth 1 https://github.com/ivanshtokov/copilot-kit

Made for: GitHub Copilot.

Per session 339 This file is loaded in full into every session.
When invoked 339 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00339 $0.00339
Opus 5 $0.00169 $0.00169
Sonnet 5 $0.00068 $0.00068
Haiku 4.5 $0.00034 $0.00034

Measured yesterday against content hash f34bcfd146c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

copilot-kit 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 yesterday.

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/testing.instructions.md · 62 lines

What it actually says

Testing Standards

🎯 Before Writing Tests

READ: .github/skills/testing-patterns/SKILL.md

📊 Testing Pyramid

        /\          E2E (Few) - Critical user flows
       /  \         
      /----\        Integration (Some) - API, DB
     /      \       
    /--------\      Unit (Many) - Functions, classes

✅ AAA Pattern (Always Use)

// Arrange - Set up test data
const user = createMockUser();

// Act - Execute code under test
const result = await getUserById(user.id);

// Assert - Verify outcome
expect(result).toEqual(user);

📋 Naming Convention

describe('UserService', () => {
  describe('getUserById', () => {
    it('should return user when found', () => {});
    it('should throw NotFoundError when user does not exist', () => {});
    it('should handle invalid id gracefully', () => {});
  });
});

🎯 What to Test

✅ Test ❌ Don't Test
Business logic Framework code
Edge cases Third-party libs
Error handling Simple getters
User-visible behavior Implementation details

🔧 Mocking Rules

  • Mock external APIs and databases
  • Mock time/random for determinism
  • Don't mock the code under test
  • Use factories for test data
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. yesterday First seen · 62 lines · 339 tokens per session scan A f34bcfd146c5

Subscribe to this mod's changes

copilot-kit testing.instructions.md is an instructions file published in the GitHub repository ivanshtokov/copilot-kit (2 stars, last pushed 7mo ago), licensed MIT. It adds 339 tokens to every session, about $0.0017 per session on Opus 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

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

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 · 6,785 tokens

next.js 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,296 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain 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,345 tokens