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 fubits1/svelte-skills --skill js-configgit clone --depth 1 https://github.com/fubits1/svelte-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/fubits1/svelte-skills/js-config)<a href="https://agentmods.dev/skills/fubits1/svelte-skills/js-config"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/js-config/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/fubits1/svelte-skills/js-config"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/js-config.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.00055 | $0.00860 |
| Opus 5 | $0.00028 | $0.00430 |
| Sonnet 5 | $0.00011 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
js-config 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 10d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JS Config
Actionable decisions for JS/TS toolchain configuration.
ESLint + Prettier: What To Do
Scenario: ESLint and Prettier conflict on formatting
- Run
pnpm exec eslint-config-prettier src/some-file.js - If conflicts found, add
eslint-config-prettier. See eslint-prettier.md for flat config setup. - If no conflicts, ESLint config has no formatting rules. Nothing to fix.
Scenario: Should I add/keep eslint-config-prettier?
- Only needed if ESLint has active formatting rules (indent, quotes, semi, comma-dangle, etc.)
- Modern
recommendedconfigs enable zero formatting rules - Legacy configs (
airbnb,standard) enable many, so you need it - Verify:
pnpm exec eslint-config-prettier src/some-file.js
Scenario: Knip/audit flags eslint-config-prettier as unused
- If not imported in
eslint.config.js, it has zero effect. Safe to remove. - If imported but CLI checker finds no conflicts, safe to remove.
Three different packages: know which is which
| Package | What it does | When to use |
|---|---|---|
eslint-config-prettier |
Turns OFF ESLint formatting rules that clash with Prettier | When ESLint config has formatting rules active |
eslint-plugin-prettier |
Runs Prettier inside ESLint as a linting rule | Rarely, slower, worse editor DX. Prefer running Prettier separately. |
svelte.configs.prettier |
Built into eslint-plugin-svelte, turns off Svelte-specific formatting rules |
When using eslint-plugin-svelte with Prettier |
Full research, flat config code examples, and sources: eslint-prettier.md
Svelte Config vs Vite Config vs Astro Config
Three config files touch Svelte/Vite behavior. Know which one owns what.
| File | What goes here | NOT here |
|---|---|---|
svelte.config.js |
Svelte compiler options, preprocessors (vitePreprocess), inspector toggle |
Vite plugins |
astro.config.mjs under vite.plugins |
Vite plugins that transform imports (SVG-as-component, YAML, devtools) | Svelte compiler options |
vite.config.js |
Only in pure Vite/SvelteKit projects. Astro owns Vite config via astro.config.mjs |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 87 lines · 55 tokens per session scan A 66c8cebb7a56
js-config is a skill published in the GitHub repository fubits1/svelte-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 860 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…