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-autocompletegit 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-autocomplete)<a href="https://agentmods.dev/skills/jiaiyan/element-plus-skills/el-autocomplete"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-autocomplete/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-autocomplete"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-autocomplete.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.01035 |
| Opus 5 | $0.00015 | $0.00517 |
| Sonnet 5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
el-autocomplete 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 12d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autocomplete Component
Autocomplete provides input suggestions based on user input.
When to Use
- Search suggestions
- Form autocomplete
- Address inputs
- Quick selection from options
Basic Usage
<template>
<el-autocomplete
v-model="state"
:fetch-suggestions="querySearch"
clearable
placeholder="Please input"
@select="handleSelect"
/>
</template>
<script setup>
import { ref, onMounted } from 'vue'
const state = ref('')
const links = ref([])
const querySearch = (queryString, cb) => {
const results = queryString
? links.value.filter(createFilter(queryString))
: links.value
cb(results)
}
const createFilter = (queryString) => {
return (restaurant) => {
return (
restaurant.value.toLowerCase().indexOf(queryString.toLowerCase()) === 0
)
}
}
const handleSelect = (item) => {
console.log(item)
}
onMounted(() => {
links.value = [
{ value: 'vue', link: 'https://github.com/vuejs/vue' },
{ value: 'element', link: 'https://github.com/ElemeFE/element' },
{ value: 'cooking', link: 'https://github.com/ElemeFE/cooking' }
]
})
</script>
Custom Template
<template>
<el-autocomplete
v-model="state"
:fetch-suggestions="querySearch"
placeholder="Please input"
>
<template #default="{ item }">
<div class="value">{{ item.value }}</div>
<span class="link">{{ item.link }}</span>
</template>
</el-autocomplete>
</template>
Remote Search
<template>
<el-autocomplete
v-model="state"
:fetch-suggestions="querySearchAsync"
placeholder="Please input"
/>
</template>
<script setup>
import { ref } from 'vue'
const state = ref('')
const querySearchAsync = (queryString, cb) => {
fetch(`/api/search?q=${queryString}`)
.then(res => res.json())
.then(data => cb(data))
}
</script>
API Reference
Attributes
| Name | Description | Type | Default |
|---|---|---|---|
| model-value / v-model | Binding value | string |
— |
| placeholder | Placeholder | string |
— |
| disabled | Whether disabled | boolean |
false |
| value-key | Key for display value | string |
'value' |
| debounce | Debounce delay (ms) | number |
300 |
| placement | Popup placement | Placement enum | 'bottom-start' |
| fetch-suggestions | Method to fetch suggestions | (queryString, cb) => void |
— |
| popper-class | Custom popup class | string |
— |
| trigger-on-focus | Trigger on focus | boolean |
true |
| name | Native name attribute | string |
— |
| select-when-unmatched | Select on enter even if no match | boolean |
false |
| label | Label text | string |
— |
| hide-loading | Hide loading icon | boolean |
false |
| popper-append-to-body | Append popup to body | boolean |
true |
| highlight-first-item | Highlight first item | boolean |
false |
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.
- 12d ago First seen · 157 lines · 29 tokens per session scan A 8c7ba551bff2
el-autocomplete is a skill published in the GitHub repository jiaiyan/element-plus-skills (25 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 1,035 once invoked, about $0.0001 per session on Opus 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
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.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
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.
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.