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 dhaupin/vant --skill vant-skill-test-integrationgit clone --depth 1 https://github.com/dhaupin/vantWrote 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/dhaupin/vant/vant-skill-test-integration)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-test-integration"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-test-integration/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/dhaupin/vant/vant-skill-test-integration"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-test-integration.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00347 |
| Opus 5.5 | $0.00014 | $0.00139 |
| Sonnet 5.5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
test-integration 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 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.
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.
What it actually says
Integration Test
Components working together.
When To Use
- Multi-component flows
- After unit tests pass
- Before e2e tests
What To Test
1. Database + API
test('user created in DB', async () => {
const user = await userService.create({ email: '[email protected]' })
const inDb = await db.users.find(user.id)
expect(inDb).toEqual(user)
})
2. Auth + User Service
test('login returns user', async () => {
const session = await auth.login('[email protected]', 'password')
expect(session.user.email).toBe('[email protected]')
})
3. Queue + Worker
test('job processed', async () => {
const job = await queue.add({ task: 'process' })
await worker.process(job.id)
expect(job.status).toBe('complete')
})
Output
## Integration Tests
| Flow | Status |
|------|--------|
| DB + API | [PASS/FAIL] |
| Auth + User | [PASS/FAIL] |
| Queue + Worker | [PASS/FAIL] |
### Time
[n] seconds
Role: Integration Tester
Input: Components
Output: Integration results
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 · 70 lines · 34 tokens per session scan A 7e2220e29322
test-integration is a skill published in the GitHub repository dhaupin/vant (12 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 347 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…
scout
Safely explore and adversarially test an authorized HTTP API using the scout CLI, with or without an OpenAPI spec. Use when asked to test, probe, validate, or explore an API, whether or not an OpenAPI/Swagger spec is available. Scout is the harness; you are the operator.
run-action
Explicit Codex workflow: Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as $rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with…
build-and-test
Explicit Codex workflow: Build the Expo/React Native app (local or EAS), install it, start Metro, then test a requested feature end-to-end.
check-env
Explicit Codex workflow: Check that the fenced React Native session, Metro, app target, and device inventory are ready for testing.