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/showcase-gig-platform/cursor-rules-initializer/presentation-rulegit clone --depth 1 https://github.com/showcase-gig-platform/cursor-rules-initializerWhat 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.00000 | $0.00450 |
| Opus 5 | $0.00000 | $0.00225 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
presentation-rule 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.
What it actually says
presentation層の修正をする際に適用するルール
役割
- API エンドポイントの定義
- リクエスト/レスポンスの変換
- ユースケースの呼び出し
- バリデーション
- エラーハンドリング
詳細構造と命名規則
presentation/
├── controller/ # コントローラー
│ └── api/ # API実装
│ ├── user_controller.go # Userコントローラー
│ └── order_controller.go # Orderコントローラー
├── middleware/ # ミドルウェア
│ ├── auth.go # 認証ミドルウェア
│ └── logging.go # ロギングミドルウェア
└── error/ # エラーハンドリング
└── converter.go # エラー変換
実装ポイント
- コントローラーはユースケースを呼び出すだけで、ビジネスロジックは含みません
- プロトコルバッファからリクエストへの変換を適切に行います
- validationはusecase層の役割なので、コントローラーではusecaseが要求するinputへの変換だけを行います
- ユースケース呼び出し後のエラーを適切にハンドリングします
- エラーはgRPCステータスコードに変換して返却します
- プロトコルバッファとDTOの変換を行います
実装例
- controller: user_controller.go
- error converter: converter.go
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 · 41 lines · 0 tokens per session scan A 9c73d0030732
presentation-rule is a cursor rule published in the GitHub repository showcase-gig-platform/cursor-rules-initializer (7 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 450 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-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.