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 ignaciohermosillacornejo/copilot-money-mcp --skill finance-tripgit clone --depth 1 https://github.com/ignaciohermosillacornejo/copilot-money-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/skills/ignaciohermosillacornejo/copilot-money-mcp/finance-trip)<a href="https://agentmods.dev/skills/ignaciohermosillacornejo/copilot-money-mcp/finance-trip"><img src="https://agentmods.dev/badge/skills/ignaciohermosillacornejo/copilot-money-mcp/finance-trip/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/skills/ignaciohermosillacornejo/copilot-money-mcp/finance-trip"><img src="https://agentmods.dev/badge/skills/ignaciohermosillacornejo/copilot-money-mcp/finance-trip.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 28 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00054 | $0.02500 |
| Opus 5.5 | $0.00022 | $0.01000 |
| Sonnet 5.5 | $0.00011 | $0.00500 |
| Haiku 4.5 | $0.00005 | $0.00250 |
Grade A, and why
finance-trip 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 10d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finance Trip
When to use
- The user wants to tag travel transactions for a trip
- The user asks "how much did I spend in [place]?"
- The user wants to find late-posting charges from a recent trip
Do NOT use if
- The "trip" isn't a discrete date range (it's general spending in a category) → use
/finance-pulse - The user wants Amazon-specific reconciliation → use
/amazon-sync
Track trip expenses by finding transactions in a date range, using location and merchant data to suggest which ones belong to the trip, and tagging confirmed ones. Can re-run to catch stragglers.
Guardrails
- Stage writes as a draft. Before any
create_tagorupdate_transactioncall (including tag adds viatag_ids), show the user the proposed change (new tag name, or which transactions get which tags) and wait for explicit confirmation. The "Definitely trip" batch-approval flow (Phase 3) is the carve-out — the batch must still be presented first, but per-item confirmation isn't required after the batch is approved in the same turn. - Confirmation is per-turn. A previous "go ahead" does not authorize subsequent batches. Each new batch of writes requires its own confirmation in the same turn.
Phase 1 — Scope the Trip
-
Read the user profile at
~/.claude/copilot-money/user-profile.md. If the file doesn't exist: runmkdir -p ~/.claude/copilot-money, then copyskills/user-profile.template.md(relative to the copilot-money-mcp repo root) to the profile path. First-time bootstrap may require CWD = repo root for the template read. Check Trip Tracking preferences and any existing trips. -
Get trip parameters. Ask the user or infer from context:
- Trip name: e.g., "French Polynesia", "Whistler Weekend"
- Date range: start and end date. If the user says "my Tahiti trip" and you know dates from prior conversation or tagged transactions, use those.
- Location hint: country, city, or region (optional — helps filter)
-
Check for existing trip tag. This skill writes, and
--writeimplies--live-reads, so the server is in live mode. Useget_tags_liveto see whether a tag for this trip exists, thenget_transactions_livewith thetagfilter to see if a tag already exists for this trip. If it does, this is a re-run to find stragglers — note which transactions are already tagged.
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.
- 10d ago Changed · +2 lines fe0e046e5c52
- 1mo ago Changed 91908510ef7e
- 2mo ago First seen · 142 lines · 54 tokens per session scan A c4267083bdc2
finance-trip is a skill published in the GitHub repository ignaciohermosillacornejo/copilot-money-mcp (86 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 2,500 once invoked, about $0.0002 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-30.
Other skills, from other repositories
connect-recommend
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue…
fred-economic-data
Query FRED (Federal Reserve Economic Data) API for 800,000+ economic time series from 100+ sources. Access GDP, unemployment, inflation, interest rates, exchange rates, housing, and regional data. Use for macroeconomic analysis, financial research, policy studies, economic forecasting, and academic research requiring…
tinker-training-cost
Calculates training costs for Tinker fine-tuning jobs. Use when estimating costs for Tinker LLM training, counting tokens in datasets, or comparing Tinker model training prices. Tokenizes datasets using the correct model tokenizer and provides accurate cost estimates.
alpaca-trade-api-sdk
Integrate and build on @alpacahq/alpaca-trade-api, the Alpaca JavaScript/TypeScript SDK for the Trading and Market Data APIs (the unified Alpaca client, ergonomic order builders, normalized market-data shapes, pagination, typed errors, resilience, and real-time streaming). Use when writing or reviewing code that…
okx-cex-portfolio
This skill should be used when the user asks about 'account balance', 'how much USDT do I have', 'my funding account', 'show my positions', 'open positions', 'position P&L', 'unrealized PnL', 'closed positions', 'position history', 'realized PnL', 'account bills', 'transaction history', 'trading fees', 'fee tier'…
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…