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/prepare-for-meetingnpx skills add carta/plugins --skill prepare-for-meetinggit 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/prepare-for-meeting)<a href="https://agentmods.dev/skills/carta/plugins/prepare-for-meeting"><img src="https://agentmods.dev/badge/skills/carta/plugins/prepare-for-meeting.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.1 | $0.00124 | $0.05655 |
| Opus 5 | $0.00062 | $0.02828 |
| Sonnet 5 | $0.00025 | $0.01131 |
| Haiku 4.5 | $0.00012 | $0.00566 |
Grade A, and why
prepare-for-meeting 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 6d 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
The user has a meeting coming up and two minutes to prepare. Produce a scannable one-page tear sheet: who is in the room, what our history with them is, what CRM objects are in play, and what to ask.
Scope is deliberately narrow: the next meeting with one counterparty. There is no agenda view and no date-range mode. If the user wants a week overview, say this skill briefs one meeting and ask which.
Voice — never narrate the machinery
The user asked to be prepared for a meeting. They did not ask how the brief is made, and naming the mechanics makes a bespoke brief read as something pre-baked.
Never mention in user-facing text: the template, placeholders, sections, filling or rendering, HTML, artifacts, file paths, tool names, or this skill. Per Carta writing style, favour domain terms over internal system names.
Progress lines are welcome, but phrase them in the user's world:
| Don't say | Say |
|---|---|
| "Now let me look at the template and gather CRM data." | "Pulling your history with DataStream AI…" |
| "I'll fill in the sections and render the HTML." | (say nothing — just produce the brief) |
| "Calling get_adviser_profile…" | "Checking who covers this account…" |
What ships with it
1 file 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.
- 6d ago First seen · 455 lines · 124 tokens per session scan A 5c9663ec67b6
prepare-for-meeting is a skill published in the GitHub repository carta/plugins (12 stars, last pushed today), licensed Apache-2.0. It adds 124 tokens to every session and 5,655 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
skill-iterative-loop
Run tasks in a loop until goals are met — use for iterative refinement, polling, or convergence.
skill-resume
Pick up where you left off from a previous session — use after context resets, compaction, or new conversations.
sys-configure
Configure Claude Octopus — redirects to /octo:setup interactive wizard.
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…
skill-compiler
Automatic solved-to-skill compiler — detects novel task completions and autonomously drafts new SKILL.md files. Stolen from Hermes Agent's learning loop (NousResearch, 2026-05-11).
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.