Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add carta/plugins/plugin install carta-investorsWrote 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/carta/plugins/carta-co-investors)<a href="https://agentmods.dev/skills/carta/plugins/carta-co-investors"><img src="https://agentmods.dev/badge/skills/carta/plugins/carta-co-investors/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/carta/plugins/carta-co-investors"><img src="https://agentmods.dev/badge/skills/carta/plugins/carta-co-investors.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.00115 | $0.10850 |
| Opus 5 | $0.00057 | $0.05425 |
| Sonnet 5 | $0.00023 | $0.02170 |
| Haiku 4.5 | $0.00012 | $0.01085 |
Grade A, and why
carta-co-investors 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 2d 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 — 632 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Co-investor analysis
Analyze who co-invests alongside you across your portfolio using Stock Purchase Agreement (SPA) data uploaded to Carta. Supports both interactive visual reports and direct analytical questions.
Data source
All SQL reads a single table, FUND_ADMIN.DOCUMENT_AI_RECORD — one row per
extracted entity or event, with the type-specific fields in an ATTRIBUTES
VARIANT rather than named columns. Each query opens with a prelude that pivots
it into the three relations the analysis needs, so every downstream CTE reads
exactly as it would against named columns:
| Prelude CTE | Filter |
|---|---|
spa_issuer |
RECORD_TYPE = 'company' |
spa_purchaser |
RECORD_TYPE = 'investor' |
spa_deal |
RECORD_TYPE = 'stock_purchase' |
spa_rec also filters FIRM_ID even though every query filters it again
downstream. That is deliberate: firm_id is the leading column of the table's
clustering key, so pinning it here lets Snowflake prune partitions instead of
scanning every firm's records and discarding them after the join. Measured on a
~460-SPA firm it cut Query S from 3.3 GB scanned to 765 MB and 2.65s to 1.25s.
It is safe because firm_id is constant across an extraction's records —
verified: zero extractions carry more than one distinct firm_id.
What ships with it
3 files 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.
- 2d ago Changed 0c8e1a7202d8
- 3d ago Changed · -449 lines scan B → A 1c314ade659d
- 13d ago First seen · 1,081 lines · 115 tokens per session scan B 564ac2c67168
carta-co-investors is a skill published in the GitHub repository carta/plugins (13 stars, last pushed today), licensed Apache-2.0. It adds 115 tokens to every session and 10,850 once invoked, about $0.0006 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
surf
Use this skill — NOT browser or webfetch — for ALL Surf crypto-data calls. 83 endpoints at localhost:8402/v1/surf/ covering CEX/DEX markets, on-chain SQL over 80+ ClickHouse tables (Ethereum, Base, Arbitrum, BSC, TRON, HyperEVM, Tempo), 100M+ labeled wallets, prediction markets (Polymarket + Kalshi), social/CT…
polymarket-trading
Use when the user wants to actually PLACE, manage, or redeem bets on Polymarket (not just read odds — that's the blockrunpredexon data tools). Covers setup (deposit wallet, funding, approvals), buy/sell with confirm gating, positions, redeeming winnings, geoblock handling, and the end-to-end flow.
grocery-prices
A skill to calculate grocery prices with country-specific taxes.
predexon
Use this skill — NOT browser or webfetch — for ALL Polymarket, Kalshi, Limitless, Opinion, Predict.Fun, dFlow, UMA oracle, and prediction market data. Provides structured API at localhost:8402/v1/pm/ for markets, cross-venue search, leaderboard, smart money, wallet analytics, wallet identity & clustering, UMA…
model-cost-compare
Starter: compare model costs for a described task — maps task shape to the cheapest adequate seat and shows the price spread.
release
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…