Borrowing it
Nothing to install: this file belongs to gosha70/code-copilot-team. 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/gosha70/code-copilot-team/master/adapters/github-copilot/.github/instructions/integration-testing.instructions.mdgit clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/gosha70/code-copilot-team/integration-testing)<a href="https://agentmods.dev/instructions/gosha70/code-copilot-team/integration-testing"><img src="https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/integration-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.1 | $0.00920 | $0.00920 |
| Opus 5 | $0.00460 | $0.00460 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
code-copilot-team integration-testing.instructions.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000/login How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Testing Protocol
Rules for verifying that cross-cutting features work before building on top of them.
Auth Must Be Verified Before Feature Development
Authentication is the most common source of cascading failures in multi-agent builds. Auth issues that go undetected compound as more features depend on protected routes.
After implementing auth (any strategy):
-
Verify the auth flow end-to-end:
- Login succeeds with valid credentials
- Login fails with invalid credentials
- Protected routes redirect unauthenticated users
- Session persists across page navigation
- Logout clears the session
-
Verify admin access (if applicable):
- Admin routes are accessible only to admin users
- Non-admin users are redirected or shown a 403
- The admin check works with the actual session token, not a mock
-
Do not build features on top of auth until the flow is verified. Building protected pages before confirming auth works leads to multi-session debugging cycles.
API Contract Verification
After implementing backend services or API routes:
- Test each endpoint with a real request (not just type-checking).
- Verify that request/response shapes match the contracts defined in the plan.
- Verify error responses (404, 400, 401, 500) return the expected format.
- If using an ORM, verify that database queries return the expected data shape.
Frontend-Backend Integration
After connecting frontend to backend:
- Verify that UI components call the correct API endpoints.
- Verify that loading states, error states, and empty states all render.
- Verify that mutations (create, update, delete) reflect in the UI without a page refresh.
- Check the browser console for errors — especially hydration mismatches in SSR frameworks.
Cross-Agent Integration
When multiple agents have worked in parallel:
- Check shared types — do both sides agree on the shape of shared data?
- Check imports — are agents importing from the correct paths?
- Check database state — if one agent created schema and another wrote queries, do they match?
- Run the full app — not just individual modules.
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.
- 4d ago First seen · 106 lines · 920 tokens per session scan A b9487cab8cb5
code-copilot-team integration-testing.instructions.md is an instructions file published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It adds 920 tokens to every session, about $0.0046 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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.
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.
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.
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).
spec-kit AGENTS.md
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.