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/daunteeth/woofi-pro-mcp/api-integration-rulegit clone --depth 1 https://github.com/DaunteEth/woofi-pro-mcpWrote 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/daunteeth/woofi-pro-mcp/api-integration-rule)<a href="https://agentmods.dev/rules/daunteeth/woofi-pro-mcp/api-integration-rule"><img src="https://agentmods.dev/badge/rules/daunteeth/woofi-pro-mcp/api-integration-rule.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 | $0.00319 | $0.00319 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
api-integration-rule 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 3d 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
🔗 API Integration & Modularization Rules
- Modularize per Orderly’s official categorization (see https://api.orderly.org/docs):
account.ts→/v1/account,/v1/positions,/v1/orders?status=openorders.ts→/v1/order,/v1/batch-order,/v1/algo-order,/v1/order/{id}assets.ts→/v1/asset/history,/v1/asset/holding,/v1/withdraw_requestpositions.ts→/v1/positionsliquidations.ts→/v1/liquidationfunding.ts→/v1/funding_rateswoofi.ts→{{env.WOOFI_BASE_ENDPOINT}}/evm-api/restful-api/private/*
- Clients in
src/endpoints/handle signing, headers, and JSON parsing. - No inline URLs in
index.tsor business logic—import from endpoint modules. - Orderly docs: https://orderly.network/docs/build-on-omnichain/evm-api/introduction
- WOOFi docs: https://learn.woo.org/
- Rule file name:
api-integration-rule.md.
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.
- 3d ago First seen · 21 lines · 319 tokens per session scan A b867abec1c31
api-integration-rule is a cursor rule published in the GitHub repository DaunteEth/woofi-pro-mcp (1 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 319 tokens to every session, about $0.0016 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-08-31.
Other cursor rules, from other repositories
lighter-safety
Safety contract for the Lighter MCP server. Apply whenever a lighter tool is invoked.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.