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 jiaiyan/element-plus-skills --skill el-cardgit clone --depth 1 https://github.com/jiaiyan/element-plus-skillsWrote 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/jiaiyan/element-plus-skills/el-card)<a href="https://agentmods.dev/skills/jiaiyan/element-plus-skills/el-card"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-card/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jiaiyan/element-plus-skills/el-card"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-card.svg" alt="Reviewed on agentmods" width="80" 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.00723 |
| Opus 5.5 | $0.00012 | $0.00289 |
| Sonnet 5.5 | $0.00006 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
el-card 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 2mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Card Component
Card component integrates information in a card container with optional header and footer.
When to Use
- Dashboard cards
- Content sections
- Product displays
- Information grouping
Basic Usage
<template>
<el-card>
<template #header>
<div class="card-header">
<span>Card name</span>
<el-button class="button" text>Operation button</el-button>
</div>
</template>
Card content
</el-card>
</template>
Simple Card
<template>
<el-card>
Card content without header
</el-card>
</template>
With Images
<template>
<el-card :body-style="{ padding: '0px' }">
<img src="https://example.com/image.jpg" class="image" />
<div style="padding: 14px">
<span>Yummy hamburger</span>
<div class="bottom">
<time class="time">{{ currentDate }}</time>
<el-button text class="button">Operating</el-button>
</div>
</div>
</el-card>
</template>
Shadow
<template>
<el-card shadow="always">Always show shadow</el-card>
<el-card shadow="hover">Show shadow on hover</el-card>
<el-card shadow="never">Never show shadow</el-card>
</template>
API Reference
Attributes
| Name | Description | Type | Default |
|---|---|---|---|
| header | Title of the card | string |
— |
| footer | Footer of the card | string |
— |
| body-style | CSS style of card body | CSSProperties |
— |
| header-class | Custom class of card header | string |
— |
| body-class | Custom class of card body | string |
— |
| footer-class | Custom class of card footer | string |
— |
| shadow | When to show card shadows | 'always' | 'never' | 'hover' |
'always' |
Slots
| Name | Description |
|---|---|
| default | Customize default content |
| header | Content of the Card header |
| footer | Content of the Card footer |
Common Patterns
Dashboard Card
<template>
<el-card class="dashboard-card">
<template #header>
<div class="card-header">
<span>{{ title }}</span>
<el-button link type="primary">View All</el-button>
</div>
</template>
<div class="card-content">
<el-statistic :value="value" />
</div>
</el-card>
</template>
<script setup>
defineProps({
title: String,
value: Number
})
</script>
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.
- 2mo ago First seen · 127 lines · 31 tokens per session scan A bf0f45e0e43b
el-card is a skill published in the GitHub repository jiaiyan/element-plus-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 723 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.