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/00-project-workflow)<a href="https://agentmods.dev/rules/ryoha000/launcherg/00-project-workflow"><img src="https://agentmods.dev/badge/rules/ryoha000/launcherg/00-project-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/00-project-workflow"><img src="https://agentmods.dev/badge/rules/ryoha000/launcherg/00-project-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.00521 | $0.00521 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
00-project-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
プロジェクト共通ワークフロー（Taskfileベース）
- 全体チェック:
task checkはブラウザ拡張、Tauri、Native Messaging Host を順に実行します。 - 拡張機能のチェック:
task check:browser-extensionは background / content-scripts / shared をビルド+テストします。 - Tauriのチェック:
task check:tauriはフロントエンドのformat/lint/checkと Rust のcargo check/cargo test --workspaceを実行します。 - Native Messaging Hostのチェック:
task check:native-messaging-hostはcargo check/cargo testを実行します。 - 拡張機能のビルド:
task build:extensionは Native Host バイナリ生成 → 拡張全体ビルドを行います。 - 型共有の生成:
task genは Native Messaging のRustモデルからTypeScriptを生成します。
開発ルール
- チェックは最小単位で実行: 影響範囲に応じて
check:*のサブタスクを優先実行し、全体task checkはPR前や大きな変更時に実行。 - 生成物の同期: Rustモデルを変更した場合は必ず
task genを実行して TypeScript 型を更新。 - 拡張の一貫ビルド: 拡張配布物の生成時は
task build:extensionを使用（Native Hostの再ビルドを保証）。 - CI前提のローカル整合:
task checkがローカルで通る状態でPRを作成。 - テスト方針: テストはコードから分離しディレクトリで整理し、テスト名は日本語で記述。
- 不要コード: 不要になったコードはコメントアウトせず削除する。
- PowerShell利用時のテスト: PowerShell (pwsh) ではテストをパイプで
| catしないで実行する。
参照
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 · 23 lines · 521 tokens per session scan A 8e2112c96b11
00-project-workflow is a cursor rule published in the GitHub repository ryoha000/launcherg (37 stars, last pushed 5mo ago), licensed Unlicense. It adds 521 tokens to every session, about $0.0026 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-09-12.
Other cursor rules, from other repositories
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks.
ci-cd
CI/CD pipeline patterns and deployment rules.
vios-testing-cicd
Testing and CI/CD conventions for VIOS.
vitest-config
Shared @repo/vitest-config factories - dual entries, Turbo package caching, Node vs Workers knobs.
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
test-engineer
When designing test strategy, analysing coverage, or writing tests outside the TDD cycle. Also use when working with CI pipelines or validating changes end-to-end.