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-infinite-scrollgit 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-infinite-scroll)<a href="https://agentmods.dev/skills/jiaiyan/element-plus-skills/el-infinite-scroll"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-infinite-scroll/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-infinite-scroll"><img src="https://agentmods.dev/badge/skills/jiaiyan/element-plus-skills/el-infinite-scroll.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.00034 | $0.00493 |
| Opus 5.5 | $0.00014 | $0.00197 |
| Sonnet 5.5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
el-infinite-scroll 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
InfiniteScroll Directive
InfiniteScroll loads more data when reaching the bottom of the page.
When to Use
- Infinite scrolling lists
- Lazy loading content
- Pagination on scroll
- Feed-style layouts
Basic Usage
<template>
<ul v-infinite-scroll="load" class="infinite-list">
<li v-for="i in count" :key="i" class="infinite-list-item">
{{ i }}
</li>
</ul>
</template>
<script setup>
import { ref } from 'vue'
const count = ref(0)
const load = () => {
count.value += 2
}
</script>
Disabled Loading
<template>
<ul
v-infinite-scroll="load"
:infinite-scroll-disabled="disabled"
class="infinite-list"
>
<li v-for="i in count" :key="i">{{ i }}</li>
</ul>
</template>
<script setup>
import { ref } from 'vue'
const count = ref(0)
const disabled = ref(false)
const load = () => {
if (count.value >= 20) {
disabled.value = true
return
}
count.value += 2
}
</script>
API Reference
Directive Options
| Name | Description | Type | Default |
|---|---|---|---|
| v-infinite-scroll | Load method | Function |
— |
| infinite-scroll-disabled | Disable loading | boolean |
false |
| infinite-scroll-delay | Throttle delay (ms) | number |
200 |
| infinite-scroll-distance | Trigger distance (px) | number |
0 |
| infinite-scroll-immediate | Execute immediately | boolean |
true |
Best Practices
- Use
infinite-scroll-disabledto stop loading when no more data - Set appropriate
infinite-scroll-distancefor better UX - Use with Scrollbar component for better performance
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 · 88 lines · 34 tokens per session scan A c732c9173fbb
el-infinite-scroll is a skill published in the GitHub repository jiaiyan/element-plus-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 493 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.