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 JoelLewis/finance_skills --skill exchange-connectivitygit clone --depth 1 https://github.com/JoelLewis/finance_skillsWrote 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/joellewis/finance_skills/exchange-connectivity)<a href="https://agentmods.dev/skills/joellewis/finance_skills/exchange-connectivity"><img src="https://agentmods.dev/badge/skills/joellewis/finance_skills/exchange-connectivity/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/joellewis/finance_skills/exchange-connectivity"><img src="https://agentmods.dev/badge/skills/joellewis/finance_skills/exchange-connectivity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00149 | $0.06977 |
| Opus 5 | $0.00075 | $0.03488 |
| Sonnet 5 | $0.00030 | $0.01395 |
| Haiku 4.5 | $0.00015 | $0.00698 |
Grade A, and why
exchange-connectivity 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 12d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exchange Connectivity
Core Concepts
Venue Connectivity Architecture
Trading venues expose electronic interfaces through which broker-dealers, market makers, and institutional participants submit orders and receive execution reports. The connectivity architecture between a firm and its execution venues is a foundational component of trading infrastructure.
Direct Market Access (DMA): DMA allows a firm to send orders directly to an exchange's matching engine without intermediation by another broker's order management system. The firm maintains its own FIX session (or proprietary protocol connection) with the exchange and is responsible for pre-trade risk controls. DMA is used by broker-dealers with exchange memberships and by proprietary trading firms.
Sponsored Access: In a sponsored access arrangement, a non-member firm routes orders to an exchange through a sponsoring broker-dealer's market participant identifier (MPID). The sponsoring broker is responsible for pre-trade risk controls under SEC Rule 15c3-5 (the Market Access Rule). Sponsored access may be "filtered" (orders pass through the sponsor's risk checks before reaching the exchange) or "unfiltered" (orders bypass the sponsor's systems and go directly to the exchange, with the sponsor relying on exchange-level risk controls). The SEC effectively prohibited unfiltered sponsored access through Rule 15c3-5, which requires the broker-dealer providing market access to implement risk management controls and supervisory procedures that are reasonably designed to prevent the entry of erroneous orders.
FIX Protocol Connectivity: The Financial Information eXchange (FIX) protocol is the dominant standard for order routing and execution reporting in equities, options, fixed income, and foreign exchange markets. FIX is a tag-value message format (e.g., Tag 35=D for a New Order Single, Tag 35=8 for an Execution Report). Most U.S. equity exchanges accept FIX for order entry, and FIX is the standard interface for broker-to-broker and broker-to-buy-side connectivity. FIX versions in common use include FIX 4.2 (widely supported, still in use at many venues), FIX 4.4 (added support for multi-leg instruments, allocation instructions), and FIX 5.0/FIXT 1.1 (separated transport and application layers).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 197 lines · 149 tokens per session scan A 6b497702ff01
exchange-connectivity is a skill published in the GitHub repository JoelLewis/finance_skills (184 stars, last pushed 1mo ago), licensed MIT. It adds 149 tokens to every session and 6,977 once invoked, about $0.0007 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-30.
Other skills, from other repositories
multi-nif
Integrate BeeL's multi-NIF model: one account holding many companies (fiscal identities), targeting a specific company per request, members and grants, and managed accounts (agencies / gestorías / fleets that invoice on behalf of others). Use when the integration deals with several NIFs/CIFs under one API key, the…
upgrade
Bring an existing BeeL. integration up to date: read the release notes and changelog, find which of the project's own calls the breaking changes hit, and propose the diff. Use when asked whether a BeeL integration is current, to migrate off deprecated routes, after BeeL announces changes, or periodically as…
payuni-query
A tool for checking PAYUNi transaction records through its Query API. PAYUNi is a Taiwan payment gateway, and a transaction query asks the gateway for an order’s current payment result.
usage-based-billing
Guide for charging directly per measured API call, token, storage unit, or other consumption using meters, stable usage events, aggregation, free thresholds, and metered subscriptions.
visa-best-practices
Best practices and integration guide for Visa developer APIs and payment protocols — covers platform setup, authentication, encryption, and product-specific workflows. Trigger keywords: VDP, Visa Developer Platform, VIC, Visa Intelligent Commerce, MPP, Machine Payments Protocol, X-Pay Token, Two-Way SSL, Mutual TLS…
kryptogo-pay-query
An implementation guide for querying KryptoGO Payment, a stablecoin payment service, to check individual or multiple payment records.