Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AxiosLeo/node-koappnpx agentmods add rules/axiosleo/node-koapp/testing-patternsWrote 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/rules/axiosleo/node-koapp/testing-patterns)<a href="https://agentmods.dev/rules/axiosleo/node-koapp/testing-patterns"><img src="https://agentmods.dev/badge/rules/axiosleo/node-koapp/testing-patterns/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/rules/axiosleo/node-koapp/testing-patterns"><img src="https://agentmods.dev/badge/rules/axiosleo/node-koapp/testing-patterns.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.00335 | $0.00335 |
| Opus 5.5 | $0.00134 | $0.00134 |
| Sonnet 5.5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
testing-patterns 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
Testing Patterns
Test Structure
Tests use Mocha and Chai as seen in tests/routes.tests.js:
const { expect } = require("chai");
const { Router } = require("../index");
describe("feature test case", () => {
it("should test specific functionality", () => {
// Test implementation
expect(result).not.to.be.null;
});
});
Router Testing
Test router configuration and resolution:
const { resolveRouters, getRouteInfo } = require("../src/core");
const router = new Router("/api/v1", {
method: "any",
handlers: [async () => {}],
});
const routes = resolveRouters(router);
const result = getRouteInfo(routes, "/api/v1/test");
Test Examples
See tests/bootstrap.js for comprehensive examples:
- Route handling patterns
- Request validation testing
- File upload testing
- Session management
- SSE (Server-Sent Events) testing
- Error handling scenarios
Running Tests
Available test scripts in package.json:
npm test- Run basic testsnpm run test-cov- Run tests with coveragenpm run ci- Run linting and tests with coverage
Test Coverage
Project uses NYC for code coverage reporting. Coverage reports are generated in the coverage/ directory.
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 · 62 lines · 335 tokens per session scan A a3004d7f869a
testing-patterns is a cursor rule published in the GitHub repository AxiosLeo/node-koapp (143 stars, last pushed yesterday), licensed MIT. It adds 335 tokens to every session, about $0.0013 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-08-30.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.