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/tutorialnpx skills add carta/plugins --skill tutorialgit clone --depth 1 https://github.com/carta/pluginsWhat 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.00146 | $0.04271 |
| Opus 5 | $0.00073 | $0.02135 |
| Sonnet 5 | $0.00029 | $0.00854 |
| Haiku 4.5 | $0.00015 | $0.00427 |
Grade A, and why
tutorial 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 — 528 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Carta CRM Tutorial
Prerequisites: Active Carta CRM subscription. Skill runs interactively — pause after each section for user input. All demo data is fictional.
You are leading an interactive ~5-minute tutorial for a user of the Carta CRM plugin. Present each section clearly, then pause and wait for the user to confirm before advancing. A simple "ready", "next", or "yes" is all they need to type. Be warm and practical — a colleague learning a new tool, not a certification exam.
Do NOT run any real Carta CRM data commands. All entity data in the demo
section is fictional and hardcoded. Only run the tools listed in
allowed-tools (the MCP connectivity check and the completion marker touch).
UX rules:
- Gate-based: pause after every section, wait for confirmation
- All demo data is fictional — no real CRM records are read or written during demos
- Show real natural-language phrases so the user knows what to say
- Write
.tutorial-seenmarker at wrap-up
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 · 528 lines · 146 tokens per session scan A 5911244658f9
tutorial is a skill published in the GitHub repository carta/plugins (12 stars, last pushed 4d ago), licensed Apache-2.0. It adds 146 tokens to every session and 4,271 once invoked, about $0.0007 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
html-ppt-tech-sharing
OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Built as a decision-grade AI literacy deck for engineers, dev community.
skill-ship
Package and finalize completed work for delivery — use when a feature is done and ready to ship.
pr-review-response
Teaches agents to reply to PR review comment threads after fixing issues, making resolutions traceable.
reskill
Team-wide charter and history optimization through skill extraction.
skill-creator
Create, refine, and benchmark agent skills. Use when building a new skill, updating an existing one, running evals, checking trigger quality, or improving a skill description.
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…