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/thiagoguislotti/copilot-instructions/e2e-testinggit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWrote 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/thiagoguislotti/copilot-instructions/e2e-testing)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/e2e-testing"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/e2e-testing.svg" alt="Measured on agentmods" 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 | $0.01134 | $0.01134 |
| Opus 5 | $0.00567 | $0.00567 |
| Sonnet 5 | $0.00227 | $0.00227 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
copilot-instructions e2e-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 3d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frameworks
Prefer Playwright (web); Cypress as alternative; SpecFlow (BDD .NET); xUnit/NUnit for .NET integration; Jest/Vitest for JS; configure in docker‑compose for CI/CD; use Testcontainers when possible.
// Playwright example
import { test, expect } from '@playwright/test';
test('user can login', async ({ page }) => {
await page.goto('/login');
await page.fill('[data-testid="email"]', '[email protected]');
await page.fill('[data-testid="password"]', 'password');
await page.click('[data-testid="submit"]');
await expect(page).toHaveURL('/dashboard');
});
Test Structure
MANDATORY AAA Pattern: All tests MUST follow Arrange-Act-Assert pattern for clarity and maintainability.
AAA Rules (Universal - All Languages):
- Arrange: Setup test data, mocks, preconditions, and initial state
- Act: Execute ONE operation being tested
- Assert: Verify ONE logical outcome (multiple assertions OK if related)
- Comments: Add explanatory note below AAA marker ONLY for critical/complex logic
- Simple operations: NO extra comments needed
- Complex logic: Add brief explanation of WHY or WHAT makes it critical
- Avoid: Redundant descriptions of obvious operations
// C# Example
[Test]
public async Task Should_CreateOrder()
{
// Arrange
// Setup: prepare API client and valid order
var client = _factory.CreateClient();
var order = OrderFactory.CreateValid();
// Act
// Execute: send POST request
var response = await client.PostAsJsonAsync("/orders", order);
// Assert
// Verify: successful creation with correct status
response.StatusCode.Should().Be(HttpStatusCode.Created);
var created = await response.Content.ReadAsAsync<Order>();
created.Id.Should().BeGreaterThan(0);
}
// TypeScript/Playwright Example
test('user can complete checkout', async ({ page }) => {
// Arrange
// Setup: login and add items to cart
await loginAsUser(page, '[email protected]');
await addItemToCart(page, 'product-123');
// Act
// Execute: complete checkout process
await page.click('[data-testid="checkout-btn"]');
await fillPaymentDetails(page);
await page.click('[data-testid="place-order"]');
// Assert
// Critical: verify order confirmation and inventory update
await expect(page.locator('[data-testid="order-success"]')).toBeVisible();
await expect(page).toHaveURL(/\/orders\/\d+/);
});
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.
- 3d ago First seen · 125 lines · 1,134 tokens per session scan A 324804003c20
copilot-instructions e2e-testing.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,134 tokens to every session, about $0.0057 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.
Other instructions, from other repositories
supabase studio-e2e-tests.instructions.md
Instructions for supabase/supabase, covering studio e2e test review rules, selector priority (best to worst), patterns to flag and good practices to encourage.
maui uitests.instructions.md
Instructions for dotnet/maui, covering ui testing guidelines for .net maui, ui test structure, two-project requirement, base class and infrastructure and naming conventions.
Math-To-Manim tests.instructions.md
Guidelines for writing and maintaining tests in Math-To-Manim.
solo AGENTS.md
Instructions for solo-agent/solo, covering project testing rules and project service lifecycle rules.
antigravity-testing-kit GEMINI.md
Instructions for anhtester/antigravity-testing-kit, covering gemini ai - global automation agent rules, git pull restriction rule, browser rules (mandatory), 🖥️ viewport & mode and 🔄 thứ tự debug bắt buộc (playwright mcp).
E2E Harness Self-Fixing Protocol
Rules for working with the Sir Thaddeus E2E test harness. Governs how to diagnose, fix, and verify failures without gaming the scoring system.