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 skills add ramp-public/cursor-plugin --skill manage-billsgit 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/skills/ramp-public/cursor-plugin/manage-bills)<a href="https://agentmods.dev/skills/ramp-public/cursor-plugin/manage-bills"><img src="https://agentmods.dev/badge/skills/ramp-public/cursor-plugin/manage-bills.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.00087 | $0.02363 |
| Opus 5 | $0.00044 | $0.01182 |
| Sonnet 5 | $0.00017 | $0.00473 |
| Haiku 4.5 | $0.00009 | $0.00236 |
Grade A, and why
manage-bills 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Bills
Search, inspect, and review vendor bills — submitted, draft, and pending approval — using the ramp CLI.
Non-Negotiables
- Deep links: If the response contains a
bill_urlfield, always include it when presenting bill details — it lets the user click through to the Ramp web app. If the field is absent, direct the user to the Ramp bills page instead. Use the URL matching the active CLI environment:https://app.ramp.com/billsfor production orhttps://demo.ramp.com/billsfor sandbox. Runramp envto check the current environment if unsure. - Bill amounts are in cents. Divide by 100 for display (e.g.,
350000→$3,500.00). - Bill IDs are UUIDs. Always confirm the correct bill before acting on it.
- Use
--agentfor machine-readable JSON output when parsing results programmatically. - These are read-only commands. For approvals, use
approval-dashboard. For write operations on drafts, use draft bill commands when available. - When the agent cannot complete an action (e.g., editing complex bill fields, approving a bill), hand off to the user via the
bill_urldeep link (if present) or the Ramp bills page.
Workflow
Step 1: Find bills
Start by searching or listing bills to locate the ones the user needs.
# Search by vendor name, invoice number, or payment ID
ramp bills search --query "Acme Corp" --agent
# List all bills (no query required)
ramp bills list --agent --limit 20
# Paid bills are included by default; pass --no-include_paid to exclude them
ramp bills search --query "UPS" --agent
# Paginate through results
ramp bills search --query "Acme" --page_cursor "{cursor_from_previous_response}" --agent
If the response includes a bill_url field on each bill, present it alongside the bill summary.
Step 2: Get bill details
Once you have a bill ID, pull comprehensive details:
# Full bill details (submitted bills only)
ramp bills get --bill_id "{bill_id}" --agent
# Draft bill details (not yet submitted)
ramp bills draft --bill_id "{bill_id}" --agent
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 · 223 lines · 87 tokens per session scan A 96ba49ab63a6
manage-bills is a skill published in the GitHub repository ramp-public/cursor-plugin (1 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 2,363 once invoked, about $0.0004 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 skills, from other repositories
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.