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 dannysmith/tauri-template --skill change-package-managergit clone --depth 1 https://github.com/dannysmith/tauri-templateWrote 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/dannysmith/tauri-template/change-package-manager)<a href="https://agentmods.dev/skills/dannysmith/tauri-template/change-package-manager"><img src="https://agentmods.dev/badge/skills/dannysmith/tauri-template/change-package-manager.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.1 | $0.00043 | $0.01275 |
| Opus 5 | $0.00022 | $0.00638 |
| Sonnet 5 | $0.00009 | $0.00255 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
change-package-manager 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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Switch this project's package manager to $ARGUMENTS.
If $ARGUMENTS is not exactly bun, pnpm, or npm, ask the user which package manager they want.
Command Mapping Reference
Detect the current package manager from AGENTS.md or package.json scripts. Use this table for all replacements:
| Context | npm | bun | pnpm |
|---|---|---|---|
| Install deps | npm install |
bun install |
pnpm install |
| Run script | npm run X |
bun run X |
pnpm run X |
| CI frozen install | npm ci |
bun install --frozen-lockfile |
pnpm install --frozen-lockfile |
| Add dep | npm install pkg |
bun add pkg |
pnpm add pkg |
| Add dev dep | npm install -D pkg |
bun add -D pkg |
pnpm add -D pkg |
| Remove dep | npm uninstall pkg |
bun remove pkg |
pnpm remove pkg |
| Audit | npm audit |
bun audit |
pnpm audit |
| Global install | npm install -g pkg |
bun install -g pkg |
pnpm add -g pkg |
| Execute binary | npx |
bunx |
pnpm dlx |
| Lock file | package-lock.json |
bun.lock |
pnpm-lock.yaml |
Step 1: Functional Config
package.json scripts
Read package.json. Replace the current PM's run command with the target PM's in all script values. For example, npm run typecheck becomes bun run typecheck.
tauri.conf.json
Read src-tauri/tauri.conf.json. Update beforeDevCommand and beforeBuildCommand.
GitHub Actions CI
Read .github/workflows/release.yml and apply the appropriate pattern:
Target: bun
- Replace the
Setup Node.jsstep with:- name: Setup Bun uses: oven-sh/setup-bun@v2 - Replace
npm ciwithbun install --frozen-lockfile
Target: pnpm
- Add a step before
Setup Node.js:- name: Setup pnpm uses: pnpm/action-setup@v4 - Change
cache: 'npm'tocache: 'pnpm'in the setup-node step - Replace
npm ciwithpnpm install --frozen-lockfile
Target: npm
- Ensure standard
actions/setup-node@v4withcache: 'npm' - Ensure
npm cifor install step - Remove any pnpm/bun setup steps
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.
- 7d ago First seen · 111 lines · 43 tokens per session scan A e3dbdee7bac7
change-package-manager is a skill published in the GitHub repository dannysmith/tauri-template (301 stars, last pushed 25d ago), licensed MIT. It adds 43 tokens to every session and 1,275 once invoked, about $0.0002 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
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…