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/chia-network/cadt/v2git 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/rules/chia-network/cadt/v2)<a href="https://agentmods.dev/rules/chia-network/cadt/v2"><img src="https://agentmods.dev/badge/rules/chia-network/cadt/v2.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.1 | $0.00046 | $0.00998 |
| Opus 5 | $0.00023 | $0.00499 |
| Sonnet 5 | $0.00009 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
v2 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
V2 Development Rules
Reference Files
- Database schema:
v2-schema.dat(DBML format) - Development plan:
v2-api-implementation-editable.plan.md-- if "STOP" appears, halt and wait for user feedback
Naming Conventions
- Database columns: snake_case
- API fields: camelCase, mapping directly to DB columns (e.g.,
orgUid->org_uid,metaKey->meta_key)
Paths
- CHIA_ROOT:
~/.chia/mainnet/ - CADT config:
~/.chia/mainnet/cadt/config.yaml - V2 database:
~/.chia/mainnet/cadt/v2/
Primary Keys (CRITICAL)
- Data tables: VARCHAR(36) storing UUID v4, generated via
uuid.v4()in application code - System tables: INTEGER AUTO_INCREMENT
- NEVER use INTEGER PRIMARY KEY AUTOINCREMENT for data tables
Foreign Keys
- Application-level validation only (no DB constraints)
- Check both main table AND staging table for references
Timestamps
- Managed by Sequelize (
created_at,updated_at) - Reject if provided in POST/PUT requests
API Request Patterns (CRITICAL)
- PUT requests: MUST include ALL fields, not just changed ones
- POST requests: include all required fields
- Same validation schema for CREATE and UPDATE
- Most list endpoints require
pageandlimit: Entity data endpoints (program,methodology,issuance,label,stakeholder,stakeholder-projects,unit-label,project-methodology,estimation,location,rating,co-benefit,validation,verification,staging,audit, and allaef-*tables) enforcepaginationSchema— omittingpage/limitreturns 400 ("page is required","limit is required"). Always include.query({ page: 1, limit: <N> }). projectandunitrequirepage/limitUNLESSxls=trueis also passed (XLS export mode skips pagination).- Endpoints that do NOT require pagination:
organizations,governance,offer,filestore, andhealth/*endpoints return all results withoutpage/limit.
Staging and On-Chain Data Validation (CRITICAL)
- Every record staged to
StagingV2— regardless of entry path (REST API, XLSX import, CSV batch import, split/transfer flows, or any future path) — must pass the same validation as the REST API: Joi schema, FK existence, and NOT NULL completeness. UsevalidateStagedRecordinsrc/utils/v2-staging-validation.js; do not hand-roll per-path checks. - Rationale: staged records become on-chain DataLayer values verbatim, and
every subscriber re-ingests them into models with
allowNull: falsecolumns. A single incomplete record permanently halts sync for all subscribers of the registry. StagingV2.assertChangeListNotNullCompletenessis a last-line-of-defense commit gate (NOT NULL only). It must never be the only validation on a write path.- Any new write path must call the shared validator and add a parity test proving the same invalid payload is rejected identically via the API path.
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 · 78 lines · 46 tokens per session scan A 0c662c55a2ff
v2 is a cursor rule published in the GitHub repository Chia-Network/cadt (41 stars, last pushed 2d ago), licensed Apache-2.0. It adds 46 tokens to every session and 998 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.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
query-optimization
查詢優化、EXPLAIN、index 設計與 RLS 效能測量.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.