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/gowtham012/claude-plugins/export-tokensnpx skills add gowtham012/Claude-plugins --skill export-tokensgit clone --depth 1 https://github.com/gowtham012/Claude-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/gowtham012/claude-plugins/export-tokens)<a href="https://agentmods.dev/skills/gowtham012/claude-plugins/export-tokens"><img src="https://agentmods.dev/badge/skills/gowtham012/claude-plugins/export-tokens.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.00031 | $0.00276 |
| Opus 5 | $0.00015 | $0.00138 |
| Sonnet 5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
export-tokens 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 5d 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.
What it actually says
Export design tokens from video: $ARGUMENTS
Arguments:
$0= video_path (required)$1= format:tailwind,css,figma, orall(default:all)
Steps
- Call MCP tool
mcp__video-insight__export_tokenswithvideo_path=$0,format=$1(defaultall). - Report what was generated:
| Format | File | Contents |
|---|---|---|
tailwind |
tailwind.config.js |
theme.extend.colors block |
css |
tokens.css |
:root { --color-* } variables |
figma |
figma-tokens.json |
Figma Tokens plugin JSON |
- Show a color swatch summary (hex + semantic role) and tell the user where each file was saved.
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.
- 5d ago First seen · 27 lines · 31 tokens per session scan A cd2a10552b1c
export-tokens is a skill published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 276 once invoked, about $0.0002 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
wasm-expert
WebAssembly expert for WASI, component model, Rust/C compilation, and browser integration.
css-expert
CSS expert for flexbox, grid, animations, responsive design, and modern layout techniques.
scss-style-guide
SCSS/CSS coding standards and patterns for fundamental-styles project.
component-composition
How to combine fundamental-styles components correctly - required wrappers, nesting rules, and common composition patterns.
review-pr
Review a pull request in fundamental-styles against SCSS coding standards, accessibility guidelines, BEM conventions, and project patterns. Use when the user says "review pr", "review pull request", "check pr", or provides a PR number to review.
bem-naming
BEM (Block Element Modifier) methodology and naming conventions used in fundamental-styles with real examples.