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-emptygit 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-empty)<a href="https://agentmods.dev/skills/jiaiyan/element-plus-skills/el-empty"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-empty/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-empty"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-empty.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.00030 | $0.00540 |
| Opus 5.5 | $0.00012 | $0.00216 |
| Sonnet 5.5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
el-empty 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.
What it actually says
Empty Component
Empty component provides placeholder hints for empty states with customizable images and content.
When to Use
- Empty data states
- No search results
- Placeholder content
- Error states
Basic Usage
<template>
<el-empty />
</template>
Custom Image
<template>
<el-empty image="https://example.com/empty.png" />
</template>
Image Size
<template>
<el-empty :image-size="200" />
</template>
Bottom Content
<template>
<el-empty>
<el-button type="primary">Button</el-button>
</el-empty>
</template>
Custom Description
<template>
<el-empty description="No data found">
<el-button type="primary">Add Data</el-button>
</el-empty>
</template>
API Reference
Attributes
| Name | Description | Type | Default |
|---|---|---|---|
| image | Image URL | string |
'' |
| image-size | Image size (width) | number |
— |
| description | Description text | string |
'' |
Slots
| Name | Description |
|---|---|
| default | Content as bottom content |
| image | Content as image |
| description | Content as description |
Common Patterns
Empty Table State
<template>
<el-table :data="tableData">
<el-table-column prop="name" label="Name" />
<template #empty>
<el-empty description="No data available">
<el-button type="primary" @click="fetchData">Refresh</el-button>
</el-empty>
</template>
</el-table>
</template>
Custom SVG Image
<template>
<el-empty>
<template #image>
<svg viewBox="0 0 100 100">
<!-- Custom SVG -->
</svg>
</template>
</el-empty>
</template>
Best Practices
- Provide actionable buttons in empty states
- Use descriptive messages
- Customize image size based on context
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 · 118 lines · 30 tokens per session scan A 3c05dd309eac
el-empty is a skill published in the GitHub repository jiaiyan/element-plus-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 540 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.