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.
git clone --depth 1 https://github.com/oxygen-fragment/claude-modularWrote 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/commands/oxygen-fragment/claude-modular/integration-tests)<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/integration-tests"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/integration-tests/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/commands/oxygen-fragment/claude-modular/integration-tests"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/integration-tests.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.00000 | $0.00600 |
| Opus 5.5 | $0.00000 | $0.00240 |
| Sonnet 5.5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
integration-tests 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 Tests Command
2. **Test Environment Setup**
- Configure test databases and services
- Set up service mocks and stubs
- Create test data fixtures
- Initialize test infrastructure
3. **API Integration Tests**
- Test HTTP endpoints with various inputs
- Validate request/response schemas
- Test authentication and authorization
- Verify error handling and status codes
4. **Database Integration Tests**
- Test CRUD operations
- Validate data consistency
- Test transaction handling
- Verify migration scripts
5. **Service Integration Tests**
- Test inter-service communication
- Validate message queue operations
- Test event handling and processing
- Verify distributed transaction behavior
6. **End-to-End Workflow Tests**
- Test complete user journeys
- Validate business process flows
- Test error recovery scenarios
- Verify performance under load
# Created test suites:
# - API endpoint tests
# - Database interaction tests
# - External service integration
# - Error handling scenarios
```
```bash
# Focus on specific integration type
/test:integration-tests --type=api
# API-focused testing:
# - REST endpoint validation
# - GraphQL query testing
# - Authentication flows
# - Rate limiting verification
```
```bash
# Test specific service integration
/test:integration-tests --service=payment-gateway
# Service-specific testing:
# - Payment processing flows
# - Error handling scenarios
# - Webhook verification
# - Transaction validation
```
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 · 98 lines · 0 tokens per session scan A 497df60c6127
integration-tests is a command published in the GitHub repository oxygen-fragment/claude-modular (285 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 600 tokens. 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-30.
Other commands, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
paul:verify
Guide manual user acceptance testing of recently built features.
atdd
Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.