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/ramp-public/cursor-pluginWrote 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/ramp-public/cursor-plugin/ramp-safety)<a href="https://agentmods.dev/rules/ramp-public/cursor-plugin/ramp-safety"><img src="https://agentmods.dev/badge/rules/ramp-public/cursor-plugin/ramp-safety/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/ramp-public/cursor-plugin/ramp-safety"><img src="https://agentmods.dev/badge/rules/ramp-public/cursor-plugin/ramp-safety.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.00571 | $0.00571 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
ramp-safety 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ramp safety guardrails
These rules apply whenever you act on Ramp data — through the Ramp CLI (ramp ...) or the
Ramp MCP server. They exist because Ramp tools move real money and act on a live financial
account.
Write actions
- Treat every approve, reject, payment, submit, card, or edit action as a write that cannot be undone. There is no "undo" for approvals.
- Always show the user the full item details (amount, vendor/payee, memo, date) before approving or rejecting. Never blind-approve.
- Confirm with the user before executing any write — especially bulk operations. State exactly what will change, then wait for explicit confirmation.
- Rejections require a reason. Approvals don't, but a short note is helpful.
- Respect the authenticated user's role. Most company-wide tools require admin/business-owner permissions; employees see only their own data. Surface permission errors plainly instead of retrying with different arguments.
Money formatting
Amounts are not represented consistently across resources — convert before displaying or summing:
- Transactions: formatted strings (e.g.
"$1,048.25","-$259.49"). Strip$and,before sorting or totaling. A leading-$is a refund — include it but call it out. - Bills: numeric dollars (e.g.
15000). Use directly, no parsing. - Reimbursements: dollars.
- Purchase order amounts: numeric.
There is no unified spend endpoint — card charges (transactions) and bill payments (bills) are separate. Query both for complete vendor spend. Always show a currency symbol and two decimals when presenting amounts.
Reading data
- Paginate every list/queue until the cursor is exhausted (
next_page_cursor/page_cursor) — a single page rarely returns everything. - Merchant/vendor names are not normalized (e.g. "Delta Air Lines" vs "Delta Airlines").
Watch for variants, dedupe by stable IDs (e.g.
transaction_uuid), and flag likely merges. - Sort queues by highest dollar amount first when presenting them for review.
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.
- 1mo ago First seen · 54 lines · 571 tokens per session scan A f56ffcc4fec1
ramp-safety is a cursor rule published in the GitHub repository ramp-public/cursor-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 571 tokens to every session, about $0.0023 per session on Opus 5.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.
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 │ └─────────────────┘…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.