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 rules/inventwo/iobroker.autodarts/testinggit clone --depth 1 https://github.com/inventwo/ioBroker.autodartsWrote 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/inventwo/iobroker.autodarts/testing)<a href="https://agentmods.dev/rules/inventwo/iobroker.autodarts/testing"><img src="https://agentmods.dev/badge/rules/inventwo/iobroker.autodarts/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.00000 | $0.00407 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
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 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.
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
Use only @iobroker/testing for integration tests — https://github.com/ioBroker/testing
Unit tests use Mocha (not Jest).
Scripts
npm run test— unit (test:js) + package validation (CI default)npm run test:js— Mocha unit tests (*.test.js,test/**)npm run test:package— validates package.json, io-package.json, admin JSONnpm run test:integration— integration tests via dev-server (local only)
Integration test pattern
const path = require("node:path");
const { tests } = require("@iobroker/testing");
tests.integration(path.join(__dirname, ".."), {
defineAdditionalTests({ suite }) {
suite("Test adapter with specific configuration", (getHarness) => {
let harness;
before(() => { harness = getHarness(); });
it("should configure and start adapter", function () {
return new Promise(async (resolve, reject) => {
// configure via harness.objects.setObject()
// start via harness.startAdapterAndWait()
// verify via harness.states.getState() / getStateIDs()
});
}).timeout(40000);
});
}
});
Rules
- Configure via
harness.objects.setObject()before start - Start via
harness.startAdapterAndWait() - Verify via
harness.states.getState()/getStateIDs() - Plan sufficient timeouts for async operations
- Mock external APIs in unit tests; never bypass the harness
- Never test Board Manager URLs directly in integration tests
CI order
Lint first (check-and-lint), then adapter-tests — adapter tests do not run if lint fails.
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 · 56 lines · 0 tokens per session scan A 158ae8e06db2
testing is a cursor rule published in the GitHub repository inventwo/ioBroker.autodarts (4 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 407 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-31.
Other cursor rules, from other repositories
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
spec
Shared RSpec conventions for the gem suite.
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.
rule-calling-help
Utility for remembering how to call VAN QA rules.