cursorrules

A project ruleset for an Android Openship client. Openship is a self-hosted deployment platform, and this client uses Kotlin Multiplatform, Compose Multiplatform, MCP, and server-sent events.

In plain words
What is it for?
Use it when working on the client's shared code, Android interface, MCP operations, live build logs, serialization, or dependency injection.
Why use it?
It keeps shared and Android-only code, networking, data models, and live updates consistent with the project's architecture.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/kareemessam09/openship-app/cursorrules
Clone the repo
git clone --depth 1 https://github.com/kareemessam09/Openship-App

Made for: Cursor.

Per session 682 This file is loaded in full into every session.
When invoked 682 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00682 $0.00682
Opus 5 $0.00341 $0.00341
Sonnet 5 $0.00136 $0.00136
Haiku 4.5 $0.00068 $0.00068

Measured 2d ago against content hash 57edb2f7cd77, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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.

.cursorrules · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Openship-App — Cursor AI Rules

Project

Unofficial Android client for Openship (self-hostable deployment platform). KMP + Compose Multiplatform. MCP as primary API layer, SSE for real-time streams.

Tech Stack

  • Kotlin 2.4.10, Compose Multiplatform 1.11.1, AGP 9.0.1
  • compileSdk 36, minSdk 24, JDK 21
  • Planned: Ktor 3.5.2, Kotlin MCP SDK 0.15.0, Koin 4.x, kotlinx.serialization 1.11.0
  • Package: com.kareemessam.openship (app), com.kareemessam.openship.shared (shared)

Architecture

  • shared/ (KMP): commonMain = networking (MCP + SSE), models, repository. androidMain = Keystore, OkHttp engine.
  • androidApp/ (Android): Compose UI, ViewModels, Koin DI, navigation.
  • One shared Ktor HttpClient for both MCP transport and SSE streams.
  • MCP for discrete ops (health, list projects). SSE for real-time (build logs, monitoring).

Key Rules

  • All networking code in shared/commonMain/ — no Android imports in commonMain.
  • Platform-specific code in shared/androidMain/platform/.
  • Use @Serializable data classes with Json { ignoreUnknownKeys = true } (API has no versioning).
  • SSE log event data field is base64-encoded — decode before display.
  • Track eventId/seq for deploy log resume (?since=<seq> on reconnect).
  • Don't hold MCP Client or SSE streams across backgrounding — reconnect on foreground.
  • Monitoring SSE 404s in CLOUD_MODE — hide monitor tab for cloud instances.
  • Use Ktor SSE plugin (NOT EventSource — can't set Authorization headers).
  • Add dependencies to gradle/libs.versions.toml first, then reference in build.gradle.kts.

API Endpoints (Base: {instanceUrl})

  • GET /api/health/env — discovery, public, returns authMode
  • GET /api/projects/home — list projects, PAT auth, tag project:list
  • GET /api/deployments/:id/stream — SSE build logs, PAT auth, ?since=<seq> for replay
  • GET /api/system/monitor/stream?serverId=<id> — SSE server metrics, PAT auth, 3s interval

Auth

  • PAT: Authorization: Bearer opsh_pat_<43-char base64url>
  • Modes: none (loopback), local (better-auth), cloud (PKCE OAuth)
  • Store in EncryptedSharedPreferences (Android Keystore)

Read the full file on GitHub · 51 lines

Changes

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.

  1. 2d ago First seen · 51 lines · 682 tokens per session scan A 57edb2f7cd77

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository kareemessam09/Openship-App (11 stars, last pushed 7d ago), licensed Apache-2.0. It adds 682 tokens to every session, about $0.0034 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-30.