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 agentmods add commands/ofershap/sveltekit-best-practices/auditgit clone --depth 1 https://github.com/ofershap/sveltekit-best-practicesWrote 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/commands/ofershap/sveltekit-best-practices/audit)<a href="https://agentmods.dev/commands/ofershap/sveltekit-best-practices/audit"><img src="https://agentmods.dev/badge/commands/ofershap/sveltekit-best-practices/audit.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00101 |
| Opus 5 | $0.00010 | $0.00051 |
| Sonnet 5 | $0.00004 | $0.00020 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
audit 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 5d 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.
This is a copy
89% identical to audit — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Scan the current project for SvelteKit / Svelte 5 anti-patterns and best practice violations.
For each issue found:
- Show the file and line
- Explain what's wrong
- Show the correct pattern
- Rate severity: critical / warning / info
Use the sveltekit-best-practices skill for reference on current best practices.
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.
- 5d ago First seen · 16 lines · 19 tokens per session scan A 5a722304fb45
audit is a command published in the GitHub repository ofershap/sveltekit-best-practices (13 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 101 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to audit, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
setup
Interactive setup for Svelte LSP development environment.
audit
Audit the current codebase for Tailwind CSS v4 best practice violations.
audit
Audit the current codebase for Go best practice violations.
audit
Audit the current codebase for Flutter best practice violations.
audit
Audit the current codebase for TypeScript best practice violations.
audit
Audit the current codebase for Expo / React Native best practice violations.