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-stepsgit 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-steps)<a href="https://agentmods.dev/skills/jiaiyan/element-plus-skills/el-steps"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-steps/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-steps"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-steps.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.00028 | $0.01058 |
| Opus 5.5 | $0.00011 | $0.00423 |
| Sonnet 5.5 | $0.00006 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
el-steps 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 1mo 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Steps Component
Steps component guides users through tasks in accordance with a process.
When to Use
- Wizard interfaces
- Process workflows
- Step progress indicators
- Multi-step forms
Basic Usage
<template>
<el-steps :active="active" finish-status="success">
<el-step title="Step 1" />
<el-step title="Step 2" />
<el-step title="Step 3" />
</el-steps>
<el-button @click="next">Next step</el-button>
</template>
<script setup>
import { ref } from 'vue'
const active = ref(0)
const next = () => {
if (active.value++ > 2) active.value = 0
}
</script>
With Status
<template>
<el-steps :active="1">
<el-step title="Step 1" description="Some description" />
<el-step title="Step 2" description="Some description" status="process" />
<el-step title="Step 3" description="Some description" status="wait" />
</el-steps>
</template>
Center
<template>
<el-steps :active="2" align-center>
<el-step title="Step 1" />
<el-step title="Step 2" />
<el-step title="Step 3" />
</el-steps>
</template>
With Description
<template>
<el-steps :active="1">
<el-step title="Step 1" description="Description for step 1" />
<el-step title="Step 2" description="Description for step 2" />
<el-step title="Step 3" description="Description for step 3" />
</el-steps>
</template>
With Icon
<template>
<el-steps :active="1">
<el-step title="Step 1" :icon="Edit" />
<el-step title="Step 2" :icon="Upload" />
<el-step title="Step 3" :icon="Picture" />
</el-steps>
</template>
<script setup>
import { Edit, Upload, Picture } from '@element-plus/icons-vue'
</script>
Vertical
<template>
<el-steps :active="1" direction="vertical">
<el-step title="Step 1" />
<el-step title="Step 2" />
<el-step title="Step 3" />
</el-steps>
</template>
Simple
<template>
<el-steps :active="1" simple>
<el-step title="Step 1" />
<el-step title="Step 2" />
<el-step title="Step 3" />
</el-steps>
</template>
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.
- 1mo ago First seen · 156 lines · 28 tokens per session scan A dbf75c6c541c
el-steps is a skill published in the GitHub repository jiaiyan/element-plus-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 1,058 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-09-03.
Other skills, from other repositories
shadcn-svelte
Pre-built shadcn-svelte components for json-render Svelte apps. Use when working with @json-render/shadcn-svelte, adding standard UI components to a Svelte catalog, or building Svelte web UIs with shadcn-svelte + Tailwind CSS components.
add-localization
Adds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React, Vue, Angular, or Astro Power Pages site.
vue-router-best-practices
Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.
native-to-weapp-vite-wevu-migration
A step-by-step guide for gradually moving native WeChat, Alipay, or Douyin mini-programs to weapp-vite, with an optional later move to Vue single-file components.