Borrowing it
Nothing to install: this file belongs to Chia-Network/cadt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Chia-Network/cadt/develop/.cursor/skills/cadt-testing/SKILL.mdgit clone --depth 1 https://github.com/Chia-Network/cadtWrote 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/chia-network/cadt/cadt-testing)<a href="https://agentmods.dev/skills/chia-network/cadt/cadt-testing"><img src="https://agentmods.dev/badge/skills/chia-network/cadt/cadt-testing/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/skills/chia-network/cadt/cadt-testing"><img src="https://agentmods.dev/badge/skills/chia-network/cadt/cadt-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.5 | $0.00019 | $0.00373 |
| Sonnet 5.5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
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 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.
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.shgenerates a uniqueTEST_RUN_ID, creates isolated SQLite DBs intests/test-dbs/, cleans up on exit- Environment:
NODE_ENV=test,USE_SIMULATOR=true,CW_PORT=<port> - Port isolation:
CW_PORTenv var overridesAPP.CW_PORTin 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 |
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 · 100 lines · 47 tokens per session scan A 68345155bfa2
cadt-testing is a skill published in the GitHub repository Chia-Network/cadt (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 933 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.