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/protocol-speccing)<a href="https://agentmods.dev/rules/centrifuge/api-v3/protocol-speccing"><img src="https://agentmods.dev/badge/rules/centrifuge/api-v3/protocol-speccing/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/protocol-speccing"><img src="https://agentmods.dev/badge/rules/centrifuge/api-v3/protocol-speccing.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.00559 |
| Opus 5.5 | $0.00000 | $0.00224 |
| Sonnet 5.5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
protocol-speccing 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 2mo 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocol Speccing Guidelines
When creating issue specifications for the cfg-api-v3 indexer to track updates from cfg-protocol-v3, follow these strict guidelines to ensure accuracy and consistency. The events might be local to a single domain or span across Hub and Spoke.
1. Issue Structure
- No Solution Design: Do not provide indexer solution design or architectural details in the issue unless specifically requested. Stick purely to on-chain specifications.
- Clear Headings: Use predictable sections like
## Description,## On-Chain Specifications,## Data Type Notes, and## Indexer Requirements.
2. On-Chain Flow
Break the event flow down according to the required domains (Hub, Spoke, or both).
For Cross-Chain Flows (e.g., Hub to Spoke, or Spoke to Hub)
Define the process across the two domains:
- Initiating Domain: Identify the Contract (e.g.,
Hub.solorSpoke.sol), Function, and the initiating Event (e.g.,UpdateContract). If it uses a payload, detail theabi.decodeshape andenumvalues. - Finalizing Domain: Identify the finalizing Contract (e.g.,
Spoke.sol,Hub.sol, or manager contracts), Function (e.g.,trustedCallor message handler), and the emitted Event upon completion.
For Single-Chain Flows
Define the process within its specific domain:
- Domain (Hub or Spoke): Identify the Contract.
- Identify the Function executing the state change.
- Identify the Event Emitted.
- Describe the chronological order if multiple events are triggered sequentially.
3. Data Type Notes
Explicitly highlight internal data types, and specific mapping operations. If spanning domains, highlight the differences:
- Assets: The protocol often uses
AssetId(a custom type mapped touint128). This may need to be resolved toaddress assetanduint256 tokenId. - Addresses: Be aware of encoding addresses as
bytes32(common in cross-chain payloads) which are later resolved to standardaddresstypes.
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.
- 2mo ago First seen · 50 lines · 0 tokens per session scan A 6dd6d64c1a46
protocol-speccing is a cursor rule published in the GitHub repository centrifuge/api-v3 (5 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 559 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.
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 │.
tact
Use this rule for smart contract development on TON using the TACT programming language. Always apply it when working with TACT contracts.
stacks-development
Guidelines for Stacks blockchain development.