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 skills add gosha70/code-copilot-team --skill integration-testinggit 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/skills/gosha70/code-copilot-team/integration-testing)<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/integration-testing"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/integration-testing/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.
<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/integration-testing"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/integration-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00925 |
| Opus 5.5 | $0.00009 | $0.00370 |
| Sonnet 5.5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
integration-testing 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 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.
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.
- 1mo ago First seen · 106 lines · 23 tokens per session scan A 75c184c20e18
integration-testing is a skill published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 23 tokens to every session and 925 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
deck-repro
Reproduce agent-deck bugs from an issue, transcript excerpt, or description in an isolated environment, and prove fixes with the same reproduction and a regression test. Use for a concrete agent-deck issue or candidate, verifying a fix, preparing a contributor bug-fix PR, or when deck-retro passes a candidate. Broad…
pipeline-efficiency-benchmark
A repeatable benchmark for comparing different versions of a development pipeline. It runs the same public tasks in isolated workspaces and records scores, tokens, time, tool calls, and cost.
x-qdev
A compact development workflow for a small, clearly defined code change. It keeps the requirement, initially failing tests, implementation, and real verification results in one task document, following TDD, or test-driven development.
x-verify-tech
A technical acceptance check for comparing implemented code with an approved technical design and the project's development rules. It extracts the design constraints, examines the relevant code, and reports what passed, failed, or was not verified.
x-adversarial-risk
A focused adversarial review of a software specification. It tries to find small counterexamples that would expose incorrect implementations, such as invalid state changes, crashes, duplicate actions, permission mistakes, or concurrent events.
x-qa-gate
A quality-review gate for completed development tasks. It checks the code against the request, design, tests, verification evidence, and current changes, using different review rounds for different risk levels.