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 carta/plugins --skill carta-witness-signaturesgit 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/carta-witness-signatures)<a href="https://agentmods.dev/skills/carta/plugins/carta-witness-signatures"><img src="https://agentmods.dev/badge/skills/carta/plugins/carta-witness-signatures/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-witness-signatures"><img src="https://agentmods.dev/badge/skills/carta/plugins/carta-witness-signatures.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Prompt Injection · line 22 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00058 | $0.01944 |
| Opus 5.5 | $0.00023 | $0.00778 |
| Sonnet 5.5 | $0.00012 | $0.00389 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
carta-witness-signatures 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 today.
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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
carta-cap-table:6.103.1
Witness & Spousal-Consent Signatures
Show the status of the extra signatures some equity awards need before they're fully in place.
Background
When someone is granted equity, the award sometimes needs a signature from a person other than the recipient before it's complete:
- Witness — an independent person who confirms they watched the recipient sign. This is a legal requirement in some markets.
- Spousal consent — the recipient's spouse signs to acknowledge the award. This applies where local marital-property rules give a spouse an interest in equity earned during the marriage.
Each one is tracked as a signature request tied to a single award. A request moves through these stages:
| Stage | What it means |
|---|---|
| Awaiting details | The request exists, but the witness or spouse's name and email haven't been added yet. |
| Awaiting signature | Details are in and the signing link has been sent. Waiting on the witness or spouse to sign. |
| Signed | Done — the witness or spouse has signed. |
| Expired | The signing link's deadline passed before it was signed. Signing links expire about 30 days after they're sent. |
These three awards can carry signature requests: option grants, RSAS (restricted stock awards), and PIUs (profits interest units).
When to Use
- "Did the witness sign Jordan's option grant?"
- "Which grants are still waiting on a signature?"
- "Is the spousal consent done for this award?"
- "Show me any expired signing links for this company."
- "List the outstanding witness signatures across my portfolio."
Prerequisites
- One company or one award → you need the company. Get it from
list_accounts(companies appear ascorporation_pk:entries). - A single award → you also need its type (
OPTION_GRANT,RSA, orPIU) and the award itself. The company-wide list (below) returns these, so start there if you don't already know which award you mean. - A portfolio → you need the portfolio. Get it from
list_accounts(portfolios appear asorganization_pk:entries) — this is the investor or firm view across the companies they hold or manage.
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.
- today Changed 9ab3694ebad8
- yesterday Changed 38561f6d18ae
- 4d ago Changed 26cd6f4d2f30
- 6d ago Changed e1aa700d7400
- 7d ago Changed 4aad1a0770a4
- 8d ago Changed 47853007c8a9
- 10d ago Changed b62499d37cdc
- 11d ago Changed 9a76a6a1aa88
- 12d ago Changed 329650c95716
- 13d ago First seen · 152 lines · 58 tokens per session scan A 81721be6139b
carta-witness-signatures is a skill published in the GitHub repository carta/plugins (15 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,944 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
bionic-safety-net
Unified survival infrastructure: health, finance, legal safety, circuit breakers, and structural protection against all ruin classes. The last line of defense.
tax-lens
US tax mechanics for a position or portfolio — short- vs. long-term treatment, wash-sale window check, qualified-dividend holding-period test, lot selection (specific-ID vs. FIFO), tax-loss-harvesting pairs, account placement, estimated annual tax drag — plus a --non-us module (W-8BEN, dividend withholding and treaty…
insurance-expert
Expert-level insurance systems, underwriting, claims processing, actuarial analysis, risk assessment, and insurtech solutions. Use when the user mentions underwriting, claims, actuarial, risk, or insurtech, or when the task involves Insurance Systems, Insurance Types, Standards and Regulations, or Claims Processing.
banking-expert
Expert-level banking systems, core banking, regulations, and banking technology. Use when the user mentions finance, core banking, regulations, or payments, or when the task involves Banking Systems or Key Technologies.
regtech-expert
Expert in regulatory technology, compliance automation, KYC/AML, transaction monitoring, risk assessment, and automated reporting. Use when the user mentions compliance, KYC, AML, transaction monitoring, risk assessment, or regulatory reporting, or when the task involves KYC/AML Compliance, KYC/AML Program, Regulatory…
gcp-dispute-kit
Use to assemble a dispute-grade evidence packet and ready-to-file letters after GCP API-key fraud (leaked-key abuse, runaway Gemini/Vertex charges). READ-ONLY — mutates nothing. Triggers on "dispute gcp charges", "google cloud fraud refund", "gemini api fraud dispute", "gcp billing dispute", "chargeback google cloud".