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-ponder)<a href="https://agentmods.dev/rules/centrifuge/api-v3/cfg-api-v3-ponder"><img src="https://agentmods.dev/badge/rules/centrifuge/api-v3/cfg-api-v3-ponder.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.00000 | $0.00371 |
| Opus 5 | $0.00000 | $0.00186 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
cfg-api-v3-ponder 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 7d 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
Ponder schema, config, and registries
- Do not hand-edit
generated/. Registry JSON/TS comes frompnpm update-registry(see README). - After changing
ponder.schema.ts,ponder.config.ts, or anything that affects Ponder codegen output, runpnpm codegenand commit generated outputs if the repo expects them updated. - Contract versions:
ponder.config.tsdefinescontractsV3andcontractsV3_1; mergedcontractsdrivesmultiMapperversion discovery. Deployment/migration tuning:src/config.ts(e.g.V3_1_MIGRATION_BLOCKS). - ABI/address wiring:
src/contracts.ts(decorateDeploymentContracts); chain RPCs andblocksfor block handlers:src/chains.ts. - Historical snapshots: period boundaries via
Timekeeper+src/handlers/blockHandlers.ts; event-driven snapshots viasnapshotter(see CLAUDE.md).
When adding a new onchain table, add the onchainTable in ponder.schema.ts, then implement the matching EntityService, export it, and wire handlers with multiMapper where applicable.
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.
- 7d ago First seen · 21 lines · 0 tokens per session scan A 61b8444f7fb9
cfg-api-v3-ponder is a cursor rule published in the GitHub repository centrifuge/api-v3 (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 371 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
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, loader validates into section diagnostics).
Database-Schema
Designs relational or NoSQL database schemas, defines tables/collections, fields, data types, relationships, indexes, and constraints based on application requirements.
Generate-Types
Generates type definitions (e.g., TypeScript interfaces/types, Flow types, Python type hints, GraphQL SDL types) based on examples like JSON data, API responses, database schemas, or descriptions.
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
A database performance rule that requires measuring PostgreSQL queries with EXPLAIN ANALYZE under the same user permissions and row-level security (RLS) conditions used in production.