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 Kage0x3B/svelte-advanced-datatable --skill svelte-advanced-datatable-datagit clone --depth 1 https://github.com/Kage0x3B/svelte-advanced-datatableWrote 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/kage0x3b/svelte-advanced-datatable/svelte-advanced-datatable-data)<a href="https://agentmods.dev/skills/kage0x3b/svelte-advanced-datatable/svelte-advanced-datatable-data"><img src="https://agentmods.dev/badge/skills/kage0x3b/svelte-advanced-datatable/svelte-advanced-datatable-data/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/kage0x3b/svelte-advanced-datatable/svelte-advanced-datatable-data"><img src="https://agentmods.dev/badge/skills/kage0x3b/svelte-advanced-datatable/svelte-advanced-datatable-data.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.00065 | $0.02520 |
| Opus 5.5 | $0.00026 | $0.01008 |
| Sonnet 5.5 | $0.00013 | $0.00504 |
| Haiku 4.5 | $0.00006 | $0.00252 |
Grade A, and why
svelte-advanced-datatable-data 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
svelte-advanced-datatable — data sources, search, errors
The table owns the UI; the data source owns IO. Pick the implementation that matches where the data lives, wire search
through the parser of your choice, and surface failures through onError + the errorState snippet.
1. Pick a data source
| Where the data lives | Use | Import from |
|---|---|---|
| JS array already in memory (client-side) | LocalDataSource<T> |
svelte-advanced-datatable (or /dataSource) |
| Single REST POST returning paginated rows | FetchApiDataSource<T> |
svelte-advanced-datatable (or /dataSource) |
| Any bespoke async function (GraphQL, RPC, SDK) | ApiFunctionDataSource<T> |
svelte-advanced-datatable (or /dataSource) |
| Same as above + TanStack Query caching | SvelteQueryDataSource<T> |
svelte-advanced-datatable/dataSource/svelteQuery |
| Anything else (websocket, EventSource, ...) | extend AbstractDataSource<T> and implement requestData |
svelte-advanced-datatable |
The data source is passed as a separate dataSource prop on <DataTable> — never inside config.
2. The request/response contract
Every data source receives a PaginatedListRequest<Data> on every page/sort/search change:
interface PaginatedListRequest<Data> {
start: number; // offset; respect exactly
amount: number; // page size; respect exactly
orderBy?: { columnKey: keyof Data; direction: 'asc' | 'desc' };
additionalOrderBy?: Array<{ columnKey: keyof Data; direction: 'asc' | 'desc' }>; // tiebreakers from Shift-click
searchQuery?: ParsedSearchQuery; // see Search section
}
interface PaginatedListResponse<Data> {
totalCount: number; // total after search filter, before pagination
items: Data[]; // exactly `amount` rows (or fewer on the last page)
}
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 · 262 lines · 65 tokens per session scan A 14a131534eae
svelte-advanced-datatable-data is a skill published in the GitHub repository Kage0x3B/svelte-advanced-datatable (5 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 2,520 once invoked, about $0.0003 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-31.
Other skills, from other repositories
pb-api
Operate PocketBase via its REST API. Use for CRUD operations on collections, authentication, querying records with filters, and managing PocketBase data.
shadcn-svelte
Manages shadcn-svelte components and projects — adding, updating, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn-svelte, the CLI, design-system presets, or any project with a components.json file. Also triggers for…
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.
new-entity
Create a backend entity with EF Core configuration and migration.
oat-css
Our preferred CSS framework — ultra-lightweight, semantic HTML UI library (8KB). Style web UIs with semantic HTML and minimal classes. Override with app-level SCSS only when necessary.
pwa
Use when the user asks to make a site installable, turn it into a PWA, add a service worker, add a web app manifest, enable "add to home screen", or support offline. Also use when adding favicon/app icons, iOS home-screen support (apple-mobile-web-app meta tags), or verifying PWA installability.