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.
npx agentmods add instructions/nikiforovall/github-copilot-rules/testing-xunitgit clone --depth 1 https://github.com/NikiforovAll/github-copilot-rulesWhat 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 | $0.02276 | $0.02276 |
| Opus 5 | $0.01138 | $0.01138 |
| Sonnet 5 | $0.00455 | $0.00455 |
| Haiku 4.5 | $0.00228 | $0.00228 |
Grade A, and why
github-copilot-rules testing-xunit.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 2d 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role Definition:
- Test Engineer
- Quality Assurance Specialist
General:
Description: Tests should be reliable, maintainable, and provide meaningful coverage. Use xUnit as the primary testing framework, with proper isolation and clear patterns for test organization and execution.
Requirements:
- Use xUnit as the testing framework
- Ensure test isolation
- Follow consistent patterns
- Maintain high code coverage
Test Class Structure:
- Use ITestOutputHelper for logging:
public class OrderProcessingTests(ITestOutputHelper output) { [Fact] public async Task ProcessOrder_ValidOrder_Succeeds() { output.WriteLine("Starting test with valid order"); // Test implementation } } - Use fixtures for shared state:
public class DatabaseFixture : IAsyncLifetime { public DbConnection Connection { get; private set; } public async Task InitializeAsync() { Connection = new SqlConnection("connection-string"); await Connection.OpenAsync(); } public async Task DisposeAsync() { await Connection.DisposeAsync(); } } public class OrderTests : IClassFixture<DatabaseFixture> { private readonly DatabaseFixture _fixture; private readonly ITestOutputHelper _output; public OrderTests(DatabaseFixture fixture, ITestOutputHelper output) { _fixture = fixture; _output = output; } }
Test Methods:
- Prefer Theory over multiple Facts:
public class DiscountCalculatorTests { public static TheoryData<decimal, int, decimal> DiscountTestData => new() { { 100m, 1, 0m }, // No discount for single item { 100m, 5, 5m }, // 5% for 5 items { 100m, 10, 10m }, // 10% for 10 items }; [Theory] [MemberData(nameof(DiscountTestData))] public void CalculateDiscount_ReturnsCorrectAmount( decimal price, int quantity, decimal expectedDiscount) { // Arrange var calculator = new DiscountCalculator(); // Act var discount = calculator.Calculate(price, quantity); // Assert Assert.Equal(expectedDiscount, discount); } } - Follow Arrange-Act-Assert pattern:
[Fact] public async Task ProcessOrder_ValidOrder_UpdatesInventory() { // Arrange var order = new Order( OrderId.New(), new[] { new OrderLine("SKU123", 5) }); var processor = new OrderProcessor(_mockRepository.Object); // Act var result = await processor.ProcessAsync(order); // Assert Assert.True(result.IsSuccess); _mockRepository.Verify( r => r.UpdateInventoryAsync( It.IsAny<string>(), It.IsAny<int>()), Times.Once); }
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.
- 2d ago First seen · 387 lines · 2,276 tokens per session scan A 38813e46c783
github-copilot-rules testing-xunit.instructions.md is an instructions file published in the GitHub repository NikiforovAll/github-copilot-rules (131 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 2,276 tokens to every session, about $0.0114 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-30.
Other instructions, from other repositories
github-copilot-starter accessibility.instructions.md
Guidelines for improving the accessibility of a website to ensure it is usable for everyone, including people with disabilities.
github-copilot-starter security.instructions.md
Comprehensive secure coding instructions for all languages and frameworks, based on OWASP Top 10 and industry best practices.
github-copilot-starter copilot-instructions.md
Copilot instructions for devbyray/github-copilot-starter, covering 🧱 project overview, 🎯 purpose, 🔧 general guidelines, 📚 guidelines structure and 🎯 agent skills (dynamic loading).
github-copilot-starter coding.instructions.md
Coding standards and conventions for the project, including JavaScript/TypeScript, CSS, and component structure.
github-copilot-starter ui-guidelines.instructions.md
UI guidelines for consistent, accessible, and maintainable user interfaces.
github-copilot-starter config.instructions.md
Instructions for configuration files used in the project, including .editorconfig, prettier, and eslint.