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 instructions/kareemessam09/openship-app/agents-mdgit clone --depth 1 https://github.com/kareemessam09/Openship-AppWrote 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/instructions/kareemessam09/openship-app/agents-md)<a href="https://agentmods.dev/instructions/kareemessam09/openship-app/agents-md"><img src="https://agentmods.dev/badge/instructions/kareemessam09/openship-app/agents-md.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.1 | $0.04367 | $0.04367 |
| Opus 5 | $0.02184 | $0.02184 |
| Sonnet 5 | $0.00873 | $0.00873 |
| Haiku 4.5 | $0.00437 | $0.00437 |
Grade A, and why
Openship-App AGENTS.md 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Openship-App — Agent Instructions
Source of truth for AI agents working in this repository. Read this before making any changes. For full API contract details, see README.md.
Project Overview
Openship-App is an unofficial Android client for Openship, the open-source self-hostable deployment platform. Built with Kotlin Multiplatform (KMP) and Compose Multiplatform, using the Model Context Protocol (MCP) as the primary API layer and Server-Sent Events (SSE) for real-time streaming.
- License: Apache-2.0
- Status: v0.1 read-only complete; v0.2 MCP redeploy/rollback complete; release packaging done (R8 minified per-ABI APKs). Unofficial community client.
- Relationship: Unofficial community client for Openship — not affiliated unless upstream says otherwise
Architecture & Protocol Strategy
androidApp/ (Android only) shared/ (KMP)
┌──────────────────────┐ ┌──────────────────────────────┐
│ Compose UI │ │ commonMain/ │
│ - Screens │───────────▶│ - client/ (REST, SSE, MCP) │
│ - Navigation │ │ - model/ (data classes) │
│ - ViewModels │ │ - repository/ │
│ - Koin DI │ │ - util/ │
│ - Lifecycle │ │ │
└──────────────────────┘ │ androidMain/ │
│ - platform/ (Keystore, │
│ OkHttp engine) │
└──────────────────────────────┘
Phased API design:
- Phase 1 (Active — Base v0.1.0): Resilient REST endpoints (
/api/health/env,/api/projects,/api/deployments,/api/system/servers) with parallelized coroutine fetching + SSE (Ktor SSE plugin) for real-time streams: build/deploy logs (/api/deployments/:id/stream) and host monitoring (/api/system/monitor/stream). - Phase 2 (Roadmap — v0.2.0+): Model Context Protocol (MCP) (
/api/mcp) for AI-native agent tooling and automated operations using the official Kotlin MCP SDK (io.modelcontextprotocol:kotlin-sdk-client0.15.0). - One shared
HttpClientwith infinite timeouts on streaming channels and AES-256 token persistence.
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.
- 5d ago First seen · 337 lines · 4,367 tokens per session scan A 593f2a9e5d4a
Openship-App AGENTS.md is an instructions file published in the GitHub repository kareemessam09/Openship-App (11 stars, last pushed 10d ago), licensed Apache-2.0. It adds 4,367 tokens to every session, about $0.0218 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).