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-notificationgit 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-notification)<a href="https://agentmods.dev/skills/jiaiyan/element-plus-skills/el-notification"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-notification/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-notification"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-notification.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.00029 | $0.02255 |
| Opus 5.5 | $0.00012 | $0.00902 |
| Sonnet 5.5 | $0.00006 | $0.00451 |
| Haiku 4.5 | $0.00003 | $0.00226 |
Grade A, and why
el-notification 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Element Plus Notification Component
Displays a global notification message at the corner of the page.
When to Invoke
Invoke this skill when:
- User needs to show persistent notifications
- User wants to display notifications with title and message
- User needs to position notifications at different corners
- User wants to customize notification content
- User asks about notification with HTML or VNode
Features
- Multiple Types: success, warning, info, error
- Custom Position: top-right, top-left, bottom-right, bottom-left
- Closable: Manual or auto-close
- Custom Duration: Configurable display time
- HTML Content: Support for HTML strings
- VNode Support: Render Vue components as content
- Custom Icons: Custom icon support
- Offset: Distance from screen edge
API Reference
Notification Options
| Name | Description | Type | Default |
|---|---|---|---|
| title | title | string |
'' |
| message | description text | string | VNode | Function |
'' |
| dangerouslyUseHTMLString | whether message is HTML | boolean |
false |
| type | notification type | 'primary' | 'success' | 'warning' | 'info' | 'error' |
'' |
| icon | custom icon component | string | Component |
— |
| customClass | custom class name | string |
'' |
| duration | duration before close (ms), 0 = no auto close | number |
4500 |
| position | custom position | 'top-right' | 'top-left' | 'bottom-right' | 'bottom-left' |
top-right |
| showClose | whether to show close button | boolean |
true |
| onClose | callback when closed | () => void |
— |
| onClick | callback when clicked | () => void |
— |
| offset | offset from screen edge | number |
0 |
| appendTo | which element the notification appends to | string | HTMLElement |
— |
| zIndex | initial zIndex | number |
— |
Notification Methods
| Method | Description | Parameters | Return |
|---|---|---|---|
| ElNotification | Show a notification | options |
Notification instance |
| ElNotification.success | Show success notification | message | options |
Notification instance |
| ElNotification.warning | Show warning notification | message | options |
Notification instance |
| ElNotification.info | Show info notification | message | options |
Notification instance |
| ElNotification.error | Show error notification | message | options |
Notification instance |
| ElNotification.closeAll | Close all notifications | — | — |
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 · 393 lines · 29 tokens per session scan A 6770e6ece411
el-notification is a skill published in the GitHub repository jiaiyan/element-plus-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 2,255 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.