Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yuping322/financial-services-plugins-newnpx agentmods add commands/yuping322/financial-services-plugins-new/analyze-fx-carryWrote 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/commands/yuping322/financial-services-plugins-new/analyze-fx-carry)<a href="https://agentmods.dev/commands/yuping322/financial-services-plugins-new/analyze-fx-carry"><img src="https://agentmods.dev/badge/commands/yuping322/financial-services-plugins-new/analyze-fx-carry/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/commands/yuping322/financial-services-plugins-new/analyze-fx-carry"><img src="https://agentmods.dev/badge/commands/yuping322/financial-services-plugins-new/analyze-fx-carry.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.00016 | $0.00499 |
| Opus 5 | $0.00008 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
analyze-fx-carry 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.
What it actually says
Analyze FX Carry Trade
This command uses LSEG FX pricing, forward curves, volatility surfaces, and historical data tools. See CONNECTORS.md for available tools.
Evaluate carry trade opportunities for a currency pair by combining spot rates, forward points, the carry term structure, volatility risk, and historical price context.
See the fx-carry-trade skill for domain knowledge on carry frameworks and risk metrics.
Workflow
1. Gather Input
Ask the user for:
- Currency pair (required) — e.g., USDJPY, EURUSD, AUDUSD
- Target tenor (optional, default 3M)
- Valuation date (optional, defaults to today)
2. Get the Spot Rate
Call fx_spot_price with the currency pair.
Extract: mid/bid/ask rates, bid-ask spread.
3. Price the Forward at Target Tenor
Call fx_forward_price with the pair and target tenor.
Extract: forward rate, forward points. Compute annualized carry.
4. Map the Full Carry Curve
Call fx_forward_curve (list then calculate) for the pair.
Present carry profile across tenors (ON through 1Y): forward points, annualized carry, cumulative carry. Identify the sweet-spot tenor.
5. Assess Volatility Risk
Call fx_vol_surface for the pair.
Extract: ATM vol at target tenor, 25-delta risk reversal, 25-delta butterfly.
Compute carry-to-vol ratio = annualized carry / ATM implied vol.
6. Historical Spot Context
Call tscc_historical_pricing_summaries for the pair's RIC with interval: "P1D", tenor: "1Y".
Assess: 52-week range, current position in range, trend direction.
7. Synthesize the Report
Present: carry-to-vol ratio and overall assessment, spot & forward pricing, carry term structure table, vol surface snapshot, historical context.
Output Format
Lead with the carry-to-vol ratio and overall assessment (attractive / moderate / unattractive). Follow with detailed supporting data in tables.
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 · 62 lines · 16 tokens per session scan A ab8f557c8c45
analyze-fx-carry is a command published in the GitHub repository yuping322/financial-services-plugins-new (17 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 499 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…