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/board-presentation-analysisnpx skills add Global-Slice/claude-plugin --skill board-presentation-analysisgit clone --depth 1 https://github.com/Global-Slice/claude-pluginWrote 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/global-slice/claude-plugin/board-presentation-analysis)<a href="https://agentmods.dev/skills/global-slice/claude-plugin/board-presentation-analysis"><img src="https://agentmods.dev/badge/skills/global-slice/claude-plugin/board-presentation-analysis.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.00061 | $0.01063 |
| Opus 5 | $0.00030 | $0.00531 |
| Sonnet 5 | $0.00012 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
board-presentation-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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Board Presentation Analysis
Scope
Use for board decks and grant-approval packs. For company cap-table totals without a board format, use cap-table-analysis. For compliance posture without board context, use compliance-analysis. For workflow status only, use workflows-analysis.
Core Principle
Board materials should be concise, decision-oriented, and traceable to Slice data. Use the same as-of date across all tools when possible. Lead with the decision the board needs to make, then show the supporting grant and ESOP pool data.
Do not dump raw tool responses into the presentation. Aggregate first, show board-relevant tables, and keep full records or long grant lists in an appendix or future file report/export.
Required Data Pull
For a standard grant approval / ESOP pool board update:
- Fetch all offered grants with
securities_find:securityType: "grant"status: "offered"limit: 50- page with
offsetwhilehasNextis true
- Fetch ESOP/equity-pool summaries with
equity_pools_get_summariesfor the same as-of date. - Fetch
cap_table_get_summarywhen the board needs company fully diluted, outstanding, or total available pool context. - Fetch
companies_get_summarywhen a one-shot company and ESOP overview is enough or when board materials need company-level totals. - Use
grants_get_types_breakdownorgrants_get_pizza_trackerfor aggregate grant lifecycle context if the deck needs a company-wide grant pipeline view.
Only call securities_get_one for specific offered grants that need full terms, documents, vesting details, valuation, or tax-treatment context.
Offered Grants Section
Use offered grants to build a proposed approval table. Include only fields needed for board review:
- Stakeholder name and stakeholder/customer-facing ID when available.
- Grant customer-facing ID and internal ID for traceability.
- Grant type.
- Quantity / total granted.
- Equity plan or share class when available.
- Grant date or proposed date when available.
- Vesting summary when available or required.
- Tax treatment and country only when relevant for approval or compliance.
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 · 82 lines · 61 tokens per session scan A f76bb83333d4
board-presentation-analysis is a skill published in the GitHub repository Global-Slice/claude-plugin (9 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,063 once invoked, about $0.0003 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
researchers-financial
Researches SEC filings, earnings calls, analyst reports, and market data. Use when the album subject involves financial crimes, corporate stories, or market events.
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.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.