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/global-slice/claude-plugin/cap-table-analysisnpx skills add Global-Slice/claude-plugin --skill cap-table-analysisgit clone --depth 1 https://github.com/Global-Slice/claude-pluginWhat 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.00079 | $0.01377 |
| Opus 5 | $0.00039 | $0.00688 |
| Sonnet 5 | $0.00016 | $0.00275 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
cap-table-analysis 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cap Table Analysis
Scope
Use for company or stakeholder ownership, ESOP pools, share classes, and rounds. For single-security deep dives or vesting timelines, use securities-analysis. For employee grant compensation or PTEP, use equity-compensation-analysis. For exit proceeds, use waterfall-analysis.
Ground Truth And Calculation Modes
Slice data is the source of truth for specific cap-table answers. Stay scoped to the authenticated company tenant and keep every analysis anchored to the same as-of date when possible.
Always label the calculation mode:
- Outstanding: issued shares on the legal share register.
- Fully diluted: issued shares plus share-settled grants, warrants, and convertibles where applicable.
- As-converted: preferred shares converted into ordinary-equivalent shares using the current conversion ratio.
Use assumptions only as a last resort and state them. Common defaults are private company, current tenant only, and equity-based awards.
Company-Level Workflow
For cap-table-wide questions:
- Use
companies_get_summaryfor a one-shot company snapshot: company identity, total stakeholders, total grants, outstanding and fully diluted shares, and ESOP pool breakdown. - Use
cap_table_get_summaryfor cap-table aggregates: company outstanding, company fully diluted, total available pool, totals by security type, and totals by share class. - Use
ownership_get_company_breakdownwhen the question is specifically about outstanding vs fully diluted ownership totals. - Use
share_classes_listandrounds_listto explain the share-class and funding-round structure behind the cap table. - Use
rounds_get_total_raisedonly after discovering the round's share class IDs withrounds_list. - Use
cap_table_search_entriesfor paginated per-stakeholder cap-table rows when aggregate totals are not enough.
Prefer cap_table_get_summary before cap_table_search_entries; it is cheaper and already includes the high-level share-class and security-type breakdowns.
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 First seen · 85 lines · 79 tokens per session scan A 6514daa6bac9
cap-table-analysis is a skill published in the GitHub repository Global-Slice/claude-plugin (9 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,377 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-31.
Other skills, from other repositories
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
auto-animate
AutoAnimate (@formkit/auto-animate) zero-config animations for React. Use for list transitions, accordions, toasts, or encountering SSR errors, animation libraries complexity.
api-design-principles
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
base-ui-react
MUI Base UI unstyled React components with Floating UI. Use for accessible components, Radix UI migration, render props API, or encountering positioning, popup, v1.0 rc / pre-GA issues.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.