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 skills/dannysmith/tauri-template/initnpx skills add dannysmith/tauri-template --skill initgit clone --depth 1 https://github.com/dannysmith/tauri-templateWhat 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.00036 | $0.00794 |
| Opus 5 | $0.00018 | $0.00397 |
| Sonnet 5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
init 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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping a user initialize this template for their specific application. This command is typically run once when starting a new project.
Step 1: Collect Information
Ask the user for:
- App Name: What is the name of their application?
- App Description: What does their app do? (1-2 sentences)
- Package Manager: Which package manager? (
npm,bun, orpnpm) — default isnpm
Step 2: Process and Update Files
After receiving their input:
- Reword the description to be coherent and professional
- Get GitHub username using
gh api user --jq .loginorgit config user.name - Update
package.json: Setname(kebab-case) anddescription - Update
src/index.html: Set<title>tag - Update
AGENTS.md: Update the Overview section with app name and description - Update
README.md: Replace "Tauri React Template" with app name, update description - Update
src-tauri/tauri.conf.json:productName: App nameidentifier:com.${githubUsername}.${kebab-case-app-name}windows[0].title: App namebundle.shortDescriptionandbundle.longDescriptionbundle.publisherandbundle.copyrightwith GitHub usernameplugins.updater.endpoints: Update to use their GitHub username and repo name
- Update
src-tauri/Cargo.toml:name: Kebab-case app namedescription: Their descriptionauthors: GitHub username
- Update
.github/workflows/release.yml:- Workflow
name - Release name and body references
- Workflow
- Update
docs/SECURITY.md:- Replace
YOUR_SECURITY_EMAILwith appropriate contact (or GitHub username if no email)
- Replace
- Update
docs/CONTRIBUTING.md:- Replace
YOUR_USERNAME/YOUR_REPOwith their GitHub username and repo name
- Replace
Step 3: Switch Package Manager (if needed)
If the user chose bun or pnpm (anything other than npm), run /change-package-manager <chosen-pm> to update all references across the project.
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.
- 2d ago First seen · 75 lines · 36 tokens per session scan A 3470f3350694
init is a skill published in the GitHub repository dannysmith/tauri-template (301 stars, last pushed 20d ago), licensed MIT. It adds 36 tokens to every session and 794 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.