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.
git clone --depth 1 https://github.com/ryoha000/launchergWrote 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/rules/ryoha000/launcherg/30-tauri-frontend-workflow)<a href="https://agentmods.dev/rules/ryoha000/launcherg/30-tauri-frontend-workflow"><img src="https://agentmods.dev/badge/rules/ryoha000/launcherg/30-tauri-frontend-workflow/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/rules/ryoha000/launcherg/30-tauri-frontend-workflow"><img src="https://agentmods.dev/badge/rules/ryoha000/launcherg/30-tauri-frontend-workflow.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.00000 | $0.00288 |
| Opus 5 | $0.00000 | $0.00144 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
30-tauri-frontend-workflow 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 today.
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.
What it actually says
Tauri フロントエンド ワークフロー（Svelte / TypeScript）
- コード整形/静的検査:
task check:tauri:frontend（format/lint/check を順に実行） - PR前に確認:
task check:tauriでフロント/バック（Rust）の両方の健全性を確認。 - イベント/コマンド連携: Rust側とのやり取りは
camelCaseで送信（Tauriがsnake_caseにマップ）。 - 型安全: 共有の型定義を活用し、
anyを避ける。 - コマンド実行ポリシー: まとめチェックは
task経由で実行。
分岐スタイル（TypeScript ユニオンの扱い）
switchで分岐し、defaultにconst _exhaustive: never = valueを置いて網羅性を型で保証する。if連鎖でのユニオン分岐は禁止（見落とし防止）。
参照
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.
- today First seen · 17 lines · 0 tokens per session scan A 9efb89355bd0
30-tauri-frontend-workflow is a cursor rule published in the GitHub repository ryoha000/launcherg (37 stars, last pushed 5mo ago), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 288 tokens. 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-09-12.
Other cursor rules, from other repositories
sveltekit-tailwindcss-typescript-cursorrules-promp
Cursor rules for SvelteKit development with Tailwind CSS and TypeScript integration.
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
frontend
You are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, Ant Design Vue, and UnoCSS, with a deep understanding of best practices and performance optimization techniques in these technologies.
project-overview
A project overview for a uni-app application built with Vue 3, TypeScript, Vite, and UnoCSS. It explains the supported platforms, main folders, configuration files, and development commands.
code
A set of coding rules for Vue 3 components written with TypeScript. It covers component structure, typed properties and events, reusable composables, and stylesheet conventions.
structure
A set of frontend project rules for organizing files, naming code, using TypeScript, and structuring Vue components. It specifies locations and conventions for components, styles, API code, utilities, types, imports, and exports.