What is cadt-testing?

A testing skill for running CADT integration tests and live API tests, including cleaning up test data. Integration tests check how multiple parts of a system work together; live API tests use a real server.

Use it to run CADT version 1 or version 2 integration tests, live API tests, or test-data cleanup.

It specifies the correct commands, isolated test databases, ports, and environment settings, avoiding interference between test runs.

cadt-testing — Skill for Cursor by Chia-Network: A testing skill for running CADT integration tests and…

Install

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.

agentmods

npx agentmods add skills/chia-network/cadt/cadt-testing

Any agent

npx skills add Chia-Network/cadt --skill cadt-testing

Clone the repo

git clone --depth 1 https://github.com/Chia-Network/cadt

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chia-network/cadt/cadt-testing.svg)](https://agentmods.dev/skills/chia-network/cadt/cadt-testing)

Your own site

<a href="https://agentmods.dev/skills/chia-network/cadt/cadt-testing"><img src="https://agentmods.dev/badge/skills/chia-network/cadt/cadt-testing.svg" alt="Measured on agentmods" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 933 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00047	$0.00933
Opus 5	$0.00023	$0.00466
Sonnet 5	$0.00009	$0.00187
Haiku 4.5	$0.00005	$0.00093

Measured yesterday against content hash 68345155bfa2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

cadt-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 yesterday.

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.

.cursor/skills/cadt-testing/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CADT Testing

Prefix all commands with fnm use && per the node-environment rule.

Integration Tests (Simulation Mode)

In-memory SQLite with simulator. No CADT server, Chia, or datalayer required.

"Run the integration tests" = run both v1 and v2 in parallel

npm run test:v1 &
npm run test:v2 &
wait

V1 and V2 use different ports (31310 and 31311 via CW_PORT env var) and isolated databases (via TEST_RUN_ID), so they run safely in parallel. Do not use the combined npm test script — it runs all specs in one process, causing v1/v2 interference.

Command	Port	Test files
`npm run test:v1`	31310	`tests/integration/*/.spec.js`, `tests/resources/*/.spec.js`
`npm run test:v2`	31311	`tests/v2/integration/*/.spec.js`

How they work

run-tests.sh generates a unique TEST_RUN_ID, creates isolated SQLite DBs in tests/test-dbs/, cleans up on exit
Environment: NODE_ENV=test, USE_SIMULATOR=true, CW_PORT=<port>
Port isolation: CW_PORT env var overrides APP.CW_PORT in config-loader.js
Timeout: 300s per test

Live API Tests

Run against a real CADT server with actual Chia datalayer.

Prerequisites

CADT server running on port 31310
Chia node + datalayer running and synced
Home organization created
Empty database for POST phases (or SKIP_EMPTY_CHECK=true)
Config at ~/.chia/mainnet/cadt/config.yaml
Optional: MySQL mirror DB for mirror verification

"Run the v2 live API test" = data-short

npm run test:v2:live:data:short

Runs tests/v2/live-api/data-short.js:

Validate request failures (bad data rejected)
POST all test records, batch commit
Validate child record failures
PUT all records, batch commit
DELETE all records, batch commit

After each commit, verifies records in DB (and optionally MySQL mirror).

All live API commands

Command	Purpose
`npm run test:v2:live:data:short`	V2 short mode: batch commit per phase
`npm run test:v2:live:data:extended`	V2 extended mode: commit per endpoint
`npm run test:v1:live:data:short`	V1 short mode
`npm run test:v2:live:organization:create`	Create V2 home organization
`npm run test:v1:live:organization:create`	Create V1 home organization
`npm run test:v1:live:organization:upgrade`	Upgrade V1 org to V2
`npm run test:v2:live:organization:delete`	Delete V2 organization

Read the full file on GitHub · 100 lines

Changes

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.

yesterday First seen · 100 lines · 47 tokens per session scan A 68345155bfa2

Subscribe to this mod's changes

cadt-testing is a skill published in the GitHub repository Chia-Network/cadt (41 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 933 once invoked, about $0.0002 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-09-04.

E2E testing Testing chia-blockchain

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

run-integration-tests

Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.

dotnet/maui · 35 tokens

cli-e2e-testcase-writer

Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.

larksuite/cli · 78 tokens

cadt-testing