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 agentmods add skills/carta/plugins/add-fundraisingnpx skills add carta/plugins --skill add-fundraisinggit clone --depth 1 https://github.com/carta/pluginsWrote 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/add-fundraising)<a href="https://agentmods.dev/skills/carta/plugins/add-fundraising"><img src="https://agentmods.dev/badge/skills/carta/plugins/add-fundraising.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 | $0.00080 | $0.00883 |
| Opus 5 | $0.00040 | $0.00441 |
| Sonnet 5 | $0.00016 | $0.00177 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
add-fundraising 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 4d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Help the user create one or more fundraising records in the Carta CRM using the
create_fundraising MCP tool. Collect details conversationally, then call the tool.
Step 1 — Fetch available stages (optional but recommended)
Call the stages tool so the user can pick a stage by name:
crm_call_tool({ "name": "crm:get_fundraising_stages", "arguments": {} })
Present the stage names to the user. If the call fails, proceed without it — stage defaults to the first stage if omitted.
Step 2 — Discover available custom fields (optional)
crm_call_tool({ "name": "crm:get_fundraising_custom_fields", "arguments": {} })
Use returned field IDs and labels as hints when collecting fundraising data. If the call fails, proceed without it.
Step 3 — Collect fundraising information
Ask the user for:
- Name (required) — the fundraising round name (e.g. "Acme Corp Series B", "Project Atlas Seed Round")
- Stage (optional) — which stage this fundraising is in (from Step 1)
- Custom fields (optional) — any fields returned in Step 2
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.
- 4d ago First seen · 92 lines · 80 tokens per session scan A 0db45b93c03b
add-fundraising is a skill published in the GitHub repository carta/plugins (12 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 883 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-30.
Other skills, from other repositories
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…
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
aspire
Build, upgrade, and operate Aspire 13.5.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting., DistributedApplication.CreateBuilder, apphost.mts…
microsoft-agent-framework
Build .NET AI agents, harnesses, and multi-agent workflows with Microsoft Agent Framework using the right agent type, sessions, tools, workflows, hosting protocols, and enterprise guardrails. USE FOR: building or reviewing .NET code that uses Microsoft.Agents., Microsoft.Extensions.AI, AIAgent, HarnessAgent…
wpf
Build and modernize WPF applications on .NET with correct XAML, data binding, commands, threading, styling, and Windows desktop migration decisions. USE FOR: working on WPF UI, MVVM, binding, commands, or desktop modernization; migrating WPF from .NET Framework to .NET; integrating newer Windows capabilities into a…
worker-services
Build long-running .NET background services with BackgroundService, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting…