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 rules/kazunarinakayama/raycast-extensions/development-flowgit clone --depth 1 https://github.com/KazunariNakayama/raycast-extensionsWrote 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/kazunarinakayama/raycast-extensions/development-flow)<a href="https://agentmods.dev/rules/kazunarinakayama/raycast-extensions/development-flow"><img src="https://agentmods.dev/badge/rules/kazunarinakayama/raycast-extensions/development-flow.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 | $0.00421 | $0.00421 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
development-flow 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 4d 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.
What it actually says
Development Flow (Spec → Scaffold → Fill)
開発の流れ
1. SPEC（仕様）
- 要件を明確にする
- I/O 契約を定義（zod スキーマ）
- UI/UX フローを決定
- エラーケースを洗い出す
2. SCAFFOLD（骨組み）
- ファイル・フォルダ構成を作成
- 空のコンポーネント・Hook・サービスを型とともに作成
- エクスポート/インポートを整理
- package.json に依存関係を追加
3. FILL（実装）
- ロジックを実装
- テストを追加（services, hooks 中心）
- 新しいパターンが生まれたら Rules を更新
編集の原則
- 関数/コンポーネント単位で編集
- diff を最小限に保つ
- 変更理由をコメントで明示（必要に応じて）
- 1 つの PR で 1 つの機能/修正
テスト戦略
services/とhooks/のロジックをテスト- Raycast UI コンポーネントは最小限のテストに留める
@raycast/apiは必要最小限を手動モック- カバレッジは 70%以上を目指す
コミット前チェックリスト
-
pnpm typecheckが通る -
pnpm lintが通る（またはpnpm lint --fixで修正） -
pnpm testが通る -
ray buildがエラーなく完了 - 秘匿値がハードコードされていない
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.
- 4d ago First seen · 46 lines · 421 tokens per session scan A 05702efcc6a1
development-flow is a cursor rule published in the GitHub repository KazunariNakayama/raycast-extensions (2 stars, last pushed 9mo ago), licensed MIT. It adds 421 tokens to every session, about $0.0021 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.