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 skills add punkadillo/figma-code-composer --skill vue-typescriptgit clone --depth 1 https://github.com/punkadillo/figma-code-composerWrote 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/punkadillo/figma-code-composer/vue-typescript)<a href="https://agentmods.dev/skills/punkadillo/figma-code-composer/vue-typescript"><img src="https://agentmods.dev/badge/skills/punkadillo/figma-code-composer/vue-typescript.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.00022 | $0.00364 |
| Opus 5 | $0.00011 | $0.00182 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
vue-typescript 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.
What it actually says
Vue.js TypeScript
You are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, Headless UI, Element Plus, and Tailwind with deep knowledge of performance optimization.
Code Style & Structure
- Write concise, maintainable, and technically accurate TypeScript code with relevant examples
- Employ functional and declarative patterns; avoid classes
- Follow DRY principles through iteration and modularization
- Use descriptive variable names with auxiliary verbs (isLoading, hasError)
- Organize files systematically with related content only
Naming Conventions
- Directories use lowercase with dashes (e.g., components/auth-wizard)
- Favor named exports for functions
TypeScript Standards
- Use TypeScript for all code; prefer interfaces over types for their extendability
- Avoid enums; use maps instead for superior type safety
- Implement functional components with TypeScript interfaces
Syntax & Formatting
- Use the "function" keyword for pure functions (hoisting benefits)
- Always employ Vue Composition API script setup style
UI & Styling
- Implement Headless UI, Element Plus, and Tailwind for components
- Mobile-first responsive design approach with Tailwind CSS
Performance Optimization
- Leverage VueUse functions for enhanced reactivity
- Wrap async components in Suspense with fallback UI
- Apply dynamic loading for non-critical components
- Optimize images: WebP format with size data and lazy loading
- Implement optimized code splitting during Vite build process
Web Vitals
Optimize for LCP, CLS, and FID using Lighthouse or WebPageTest tools.
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 · 50 lines · 22 tokens per session scan A d9890d1d3793
vue-typescript is a skill published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 19d ago), licensed MIT. It adds 22 tokens to every session and 364 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
nuxtjs-vue-typescript
Best practices for building Nuxt 3 and Vue 3 applications with TypeScript, the Composition API, and Tailwind CSS. Use when structuring Nuxt/Vue projects, writing composables, typing components and props, wiring up server routes and plugins, or optimizing Nuxt builds and Web Vitals.
inertia-rails-typescript
TypeScript type safety for Inertia Rails (React, Vue, Svelte): shared props, flash, and errors via InertiaConfig module augmentation in globals.d.ts. Use when setting up TypeScript types, configuring shared props typing, fixing TS2344 or TS2339 errors in Inertia components, or adding new shared data.
nuxt-modules
Use when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables, plugins), (4) Server extensions (API routes, middleware), (5) Releasing/publishing modules to npm, (6) Setting up CI/CD workflows for modules.…
vue-admin-skill
A planned Vue 3 and TypeScript skill for generating an administration interface: a back-office web application with pages, forms, tables, charts, navigation, and permissions. It describes a starter structure using Element Plus, Pinia, Vue Router, Vite, and related tools, but is not yet complete.
typescript-strict
Use when writing or reviewing TypeScript in Vue, Nuxt, Node, or shared TS utilities, fixing type errors, or deciding how to type API responses and composables.
fec-vue3-project-standard
A Vue 3 and TypeScript project standard covering component boundaries, composables, routing, Pinia state, API layers, errors, styles, and project structure. Vue is a frontend framework, and composables are reusable functions for sharing component logic.