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/31-router-tabs-architecture)<a href="https://agentmods.dev/rules/ryoha000/launcherg/31-router-tabs-architecture"><img src="https://agentmods.dev/badge/rules/ryoha000/launcherg/31-router-tabs-architecture/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/31-router-tabs-architecture"><img src="https://agentmods.dev/badge/rules/ryoha000/launcherg/31-router-tabs-architecture.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.00470 |
| Opus 5 | $0.00000 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
31-router-tabs-architecture 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
Router/Tab アーキテクチャ ルール（Svelte + svelte5-router）
-
単一ソース: ルート定義は
ROUTE_REGISTRY（src/router/const.ts）で一元管理。型はDescriptor（src/router/registry.ts）。kindは string とし、Tab.typeはkindと一致させる。 -
pathTemplate 規約: 宣言は
/:param(regex)形式で記述（例:/works/:id(\\d+)）。ルータ登録時のみbuildRoutes（src/router/registry.ts）が(?<param>regex)に変換して渡す。named group を直書きしない。 -
抽出/生成ヘルパ: 解析/生成は
schema.ts（src/store/tabs/schema.ts）を必ず利用。pathParamExtractor(name)/queryParamExtractor(name, editor?)queryParamExtractorは extractor 側でdecodeURIComponent済み。editor は表示用の加工のみを行う（decode を重ねない）。- ルートからタブ動作判定は
getTabActionFromLocation、URL 生成はbuildPathを使用。
-
UI の責務:
src/components/TabはROUTE_REGISTRYとbuildPathを経由して遷移し、tab.typeのハードコード分岐を持たない。 -
ルート追加の指針:
ROUTE_REGISTRYにkind/pathTemplate/component/iconを追加。- keyed ルートのタイトルが必要なら
queryParamExtractor(name, editor)を指定して表示名を生成。
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 · 25 lines · 0 tokens per session scan A ce4bdaa0a67f
31-router-tabs-architecture 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 470 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
svelte-5-vs-svelte-4-cursorrules-prompt-file
Cursor rules for comparing Svelte 5 and Svelte 4 development.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with 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.
svelte-mcp-tools
Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation.
frontend-component
Vue component structure, styling, derived state, modals, icons, DaisyUI/Tailwind frontend component conventions.
frontend
Vue frontend — components, Vitest, generated API client, apiCallWithLoading, DaisyUI. Read this first for any frontend work.