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.
git clone --depth 1 https://github.com/centrifuge/api-v3Wrote 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/centrifuge/api-v3/cfg-api-v3-handlers)<a href="https://agentmods.dev/rules/centrifuge/api-v3/cfg-api-v3-handlers"><img src="https://agentmods.dev/badge/rules/centrifuge/api-v3/cfg-api-v3-handlers/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/centrifuge/api-v3/cfg-api-v3-handlers"><img src="https://agentmods.dev/badge/rules/centrifuge/api-v3/cfg-api-v3-handlers.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.00000 | $0.00414 |
| Opus 5 | $0.00000 | $0.00207 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
cfg-api-v3-handlers 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 8d 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
Handlers (src/handlers/)
- Thin orchestration only: decode
event.args, resolve IDs, call services. Put business rules insrc/services/. - No database access: do not use
context.db, Drizzleeq/and/.insert, or SQL. Use entity services (FooService.get,query,upsert,save,insertMany,saveMany, …). - Snapshot rows: use
snapshotterfromsrc/helpers/snapshotter.tswith the correct snapshot table fromponder:schema— do not duplicate insert logic in the handler. - Contract events across versions: prefer
multiMapper("Hub:EventName", handler)over separateponder.onperHubV3/HubV3_1when the ABI matches (seesrc/helpers/multiMapper.ts). Block handlers may use **ponder.on(\${chainName}:block`, …)** like [src/handlers/blockHandlers.ts`](src/handlers/blockHandlers.ts). - Efficiency: prefer batch service APIs when updating many rows; avoid N+1 query patterns.
- Observability: use
logEventfromsrc/helpers/logger.tswhere useful for high-level event receipt (optional; services useserviceLog/serviceError). - Negative space / early exits: prefer guard clauses (
if (!x) return …) over nestedif/else. When a required lookup is missing,return(typicallyreturn serviceError(…)), then keep the success path flat.
Mirror the closest existing handler in the same domain before inventing a new structure.
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.
- 8d ago First seen · 18 lines · 0 tokens per session scan A ff7b3ad84c0d
cfg-api-v3-handlers is a cursor rule published in the GitHub repository centrifuge/api-v3 (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 414 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
solana-integration-constraints
Constraints and requirements for Solana integration with MetaMask Connect — wallet adapter config, CAIP-2 IDs, network support per platform, RPC routing, and platform limitations.
zama-protocol-zama-solidity--setups-foundry
Detailed reference for foundry (zama-solidity skill).
cardano-mcp
These rules complement our main development collaboration rules, focusing specifically on the Model Context Protocol (MCP) server project with TypeScript. This project serves as a specialized RAG (Retrieval-Augmented Generation) gateway to existing Cardano resources, documentation, and tools to assist with dApp…
elizaos_v2_onchain_plugins
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Wallet Provider│ │ Connection Mgmt │ │ Transaction Svc │ │ - Private Keys │───▶│ - RPC Endpoints │───▶│ - Tx Construction│ │ - Public Keys │ │ - Network Config │ │ - Fee Estimation│ │ - Signatures │ │ - Health Check │ │ - Broadcasting │ └─────────────────┘…
solana_core_architecture
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Entry Point │ │ Instruction │ │ Account │ │ lib.rs │───▶│ Processing │───▶│ Validation │ │ │ │ │ │ │ │ - entrypoint! │ │ - Route dispatch │ │ - Owner checks │ │ - processinst │ │ - Deserialize │ │ - Data validate │.
stacks-development
Guidelines for Stacks blockchain development.