ship AGENTS.md

Repository instructions that direct coding agents to read the adjacent CLAUDE.md file as the single source of truth.

In plain words
What is it for?
Following the project’s shared instructions during development or maintenance.
Why use it?
It prevents agents from relying on incomplete or duplicated guidance when working in the repository.

Instructions file for CodexOpenCode

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 instructions/shipstatic/ship/agents-md
Clone the repo
git clone --depth 1 https://github.com/shipstatic/ship

Made for: Codex, OpenCode.

Per session 55 This file is loaded in full into every session.
When invoked 55 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod 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.00055 $0.00055
Opus 5 $0.00028 $0.00028
Sonnet 5 $0.00011 $0.00011
Haiku 4.5 $0.00006 $0.00006

Measured yesterday against content hash 077837e6711b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ship 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 yesterday.

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.

Origin

This is a copy

97% identical to mcp AGENTS.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 6 lines

What it actually says

@shipstatic/ship — agent instructions

Read CLAUDE.md (same directory). It is the single source of truth for this repo's instructions; everything in it applies to every agent, not just Claude. Do not duplicate its content here.

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. yesterday First seen · 6 lines · 55 tokens per session scan A 077837e6711b

Subscribe to this mod's changes

ship AGENTS.md is an instructions file published in the GitHub repository shipstatic/ship (5 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to mcp AGENTS.md, differing in 2 lines, and is treated as a copy.

Related

Other instructions, from other repositories