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 skills/band-app/band/write-integration-testnpx skills add band-app/band --skill write-integration-testgit clone --depth 1 https://github.com/band-app/bandWrote 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/band-app/band/write-integration-test)<a href="https://agentmods.dev/skills/band-app/band/write-integration-test"><img src="https://agentmods.dev/badge/skills/band-app/band/write-integration-test.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.00137 | $0.05854 |
| Opus 5 | $0.00068 | $0.02927 |
| Sonnet 5 | $0.00027 | $0.01171 |
| Haiku 4.5 | $0.00014 | $0.00585 |
Grade A, and why
write-integration-test 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const res = await fetch(url, { headers: { Authorization: `Bearer ${TOKEN}` } }); How it starts
The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Integration Tests
This skill is the operational playbook — how to write an integration test against the Band web app. It is NOT the rule list.
- The reviewer-enforced rules live in
.claude/testing-criteria.mdasTEST-1…TEST-35. Open that file once before you write your first test on this repo. Both CI (.github/workflows/claude-review.yml) and the localreview-and-applyskill apply it verbatim to your diff. - The narrative doctrine — why we test this way — lives in
docs/integration-testing.md.
Throughout this playbook, prescriptions that correspond to a specific rule are cited inline as (enforces TEST-N). If you intentionally deviate from one, fix it before pushing or cite the ID in your PR description with a justification — the reviewer will flag every unjustified deviation.
Integration tests are the default proof of correctness for any user-observable change (enforces TEST-6). Unit tests stay useful for non-observable internals and combinatorial cases, but the integration test is what proves the feature works and what guards against the regression you came here to fix.
Architecture — One Picture, Both Layers
Backend and frontend tests share the same server boot and the same fixture model. The only difference is whether the test drives the server through fetch or through a browser.
┌────────────────────────────────────────────────────────────────────┐
│ Test Process │
│ │
│ ┌─────────────┐ │
│ │ Test body │── fetch ──┐ │
│ └─────────────┘ ▼ │
│ │ ┌──────────────────────────────┐ │
│ │ │ Real App Server (production │ │
│ │ │ binary, SSR, auth, tRPC, │ │
│ │ │ migrations, the works) │ │
│ │ └──────────────────────────────┘ │
│ │ │ HTTP (env var override) │
│ │ ▼ │
│ │ ┌──────────────────────────────┐ │
│ │ │ Express stubs (one server │ │
│ │ │ per external service, on │ │
│ │ │ a random port) │ │
│ │ └──────────────────────────────┘ │
│ │ │
│ Frontend tests ONLY: │
│ ┌─────────────────────┐ drives │
│ │ Playwright Browser │ ◄────────────── Test body │
│ │ (Chromium, real) │ │
│ └─────────────────────┘ │
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Testcontainers / temp SQLite — real data layer, ephemeral │ │
│ └──────────────────────────────────────────────────────────────┘ │
└────────────────────────────────────────────────────────────────────┘
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 · 479 lines · 137 tokens per session scan A c2b03797ff33
write-integration-test is a skill published in the GitHub repository band-app/band (5 stars, last pushed 4d ago), licensed MIT. It adds 137 tokens to every session and 5,854 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…