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-alertgit 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-alert)<a href="https://agentmods.dev/skills/jiaiyan/element-plus-skills/el-alert"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-alert/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-alert"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-alert.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.00032 | $0.01286 |
| Opus 5.5 | $0.00013 | $0.00514 |
| Sonnet 5.5 | $0.00006 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
el-alert 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alert Component
Alert component displays important alert messages on the page. Unlike notifications, alerts are non-overlay elements that do not disappear automatically.
When to Use
- Display important system messages or warnings
- Show operation results (success, error, warning, info)
- Present non-dismissible status information
- Guide users with important instructions
Basic Usage
<template>
<el-alert title="success alert" type="success" />
<el-alert title="warning alert" type="warning" />
<el-alert title="info alert" type="info" />
<el-alert title="error alert" type="error" />
<el-alert title="primary alert" type="primary" />
</template>
Theme Variations
<template>
<el-alert title="Light theme" type="success" effect="light" />
<el-alert title="Dark theme" type="success" effect="dark" />
</template>
Customizable Close Button
<template>
<el-alert title="unclosable alert" type="success" :closable="false" />
<el-alert title="custom close text" type="info" close-text="Got it!" />
<el-alert title="with close callback" type="warning" @close="handleClose" />
</template>
<script setup>
const handleClose = (event) => {
console.log('Alert closed', event)
}
</script>
With Icon
<template>
<el-alert title="with default icon" type="success" show-icon />
<el-alert title="custom icon slot" type="warning" show-icon>
<template #icon>
<el-icon><Star /></el-icon>
</template>
</el-alert>
</template>
Centered Text
<template>
<el-alert title="centered alert" type="success" center />
</template>
With Description
<template>
<el-alert
title="with description"
type="success"
description="This is a description message with more details."
/>
</template>
Complete Example with All Features
<template>
<el-alert
title="Success Alert"
type="success"
description="Your operation was completed successfully."
show-icon
center
closable
close-text="Dismiss"
@close="handleClose"
/>
</template>
<script setup>
const handleClose = (event) => {
console.log('Alert dismissed')
}
</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 · 220 lines · 32 tokens per session scan A fe74818051a5
el-alert is a skill published in the GitHub repository jiaiyan/element-plus-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 1,286 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.