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/qauth-labs/qauth/nx-testingnpx skills add qauth-labs/qauth --skill nx-testinggit clone --depth 1 https://github.com/qauth-labs/qauthWrote 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/qauth-labs/qauth/nx-testing)<a href="https://agentmods.dev/skills/qauth-labs/qauth/nx-testing"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/nx-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 | $0.00028 | $0.00499 |
| Opus 5 | $0.00014 | $0.00249 |
| Sonnet 5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
nx-testing 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 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.
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
Nx Testing Workflows
Test Stack
- Runner: Vitest 4.x
- HTTP Testing: Supertest
- Containers: Testcontainers
- Coverage: Built-in Vitest
Running Tests
# Single project
pnpm nx test auth-server
pnpm nx test auth-server --watch
pnpm nx test auth-server --coverage
# Multiple projects
pnpm nx run-many -t test --all
pnpm nx affected -t test
pnpm nx run-many -t test --all --parallel=3
# Vitest UI
pnpm test:ui
Test File Patterns
Co-locate tests with source:
libs/server/jwt/src/
├── jwt.service.ts
├── jwt.service.spec.ts
└── index.ts
Unit Test Example
import { describe, it, expect, beforeEach } from 'vitest';
import { createService } from './service';
describe('Service', () => {
let service: ReturnType<typeof createService>;
beforeEach(() => {
service = createService();
});
it('should do something', () => {
expect(service.method()).toBe(expected);
});
});
Integration Test with Fastify
import { describe, it, expect, beforeAll, afterAll } from 'vitest';
import { buildTestApp } from '@qauth-labs/shared-testing';
import type { FastifyInstance } from 'fastify';
describe('Route', () => {
let app: FastifyInstance;
beforeAll(async () => {
app = await buildTestApp();
});
afterAll(async () => {
await app.close();
});
it('should return 200', async () => {
const response = await app.inject({
method: 'GET',
url: '/health',
});
expect(response.statusCode).toBe(200);
});
});
Best Practices
- Test business logic in isolation
- Use
@qauth-labs/shared-testingutilities - Use Testcontainers for real PostgreSQL
- Mock external services
- Name tests descriptively
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 · 97 lines · 28 tokens per session scan A 1d22abbf1cbc
nx-testing is a skill published in the GitHub repository qauth-labs/qauth (24 stars, last pushed 4d ago), licensed Apache-2.0. It adds 28 tokens to every session and 499 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
write-e2e-test
Write end-to-end (e2e) tests for authgear-server. Use when the user asks to write, add, or create e2e tests. The tests live in e2e/tests/ and are YAML-driven.
add-portal-screen
Add screens or components to the portal frontend. Use when the user asks to create a new portal page, screen, tab, or UI component.
api-design
Review or design APIs for Authgear. In review mode, evaluates a design draft against the checklist. In ideation mode, develops a design from a description and self-reviews it.
update-deps
Audit and fix dependency vulnerabilities in Go and Node.js packages. Runs govulncheck for Go and npm audit for each package.json directory. Commits fixes directory by directory.
new-siteadmin-api
Full pipeline for adding a new Site Admin API feature — from OpenAPI spec through implementation plan to working service. Use when adding a new endpoint or filling in real data for an existing stub.
update-portal-ui
Guidelines for updating or designing pages in the portal React frontend (portal/src). Covers component conventions, link rendering rules, i18n patterns, and common pitfalls.