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/moasq/agentic-ship/agents-mdgit clone --depth 1 https://github.com/moasq/agentic-shipWhat 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.11608 | $0.11608 |
| Opus 5 | $0.05804 | $0.05804 |
| Sonnet 5 | $0.02322 | $0.02322 |
| Haiku 4.5 | $0.01161 | $0.01161 |
Grade C, and why
agentic-ship AGENTS.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
**Never write `cp`, `ln`, `readlink`, `grep`, `rm -rf`, `mkdir -p`, `chmod`, `openssl`, How it starts
The opening of the file, as written. The whole thing — 726 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Ship
This is the tool-only repository. It has no bundled application, backend, assets,
or deployment. The product-stack rules below are guidance for a downstream product
workspace that adopts Agentic Ship; do not expect src/, convex/, or a local website
to exist here.
This file is where every rule is declared. CLAUDE.md imports it with one line;
.claude/skills links to .agents/skills. Skills elaborate these rules into
procedure — they must never restate one differently, and never introduce a rule that is
not declared here. When a skill and this file disagree, this file is right and the skill
is a bug.
Works with any agentic tool. Codex, Cursor, Windsurf, Cline, Copilot, Gemini CLI, and
OpenClaw (with this repository as its agent workspace) read this file natively; skills
are plain markdown any agent can follow. Canonical role
briefs live in .agents/agents/; pnpm sync:agents generates the Claude plugin's
top-level agents/, project-native Codex and Cursor agents, and non-secret Hermes and
OpenClaw profiles. Cursor gets MCP through the committed
.cursor/mcp.json mirror; Codex gets project-scoped TOML generated from the same pinned
catalog.
The repo is also an installable plugin for Claude Code and Codex — manifests in
.claude-plugin/ and .codex-plugin/ point at the same .agents/skills/, so the
plugin adds a second delivery path, never a second copy of a rule.
Per-tool matrix and sync rules: .agents/skills/agent-compatibility/SKILL.md.
Skills with a references/ folder keep their deep material there — load it only when
the task needs it.
Instructions live here. Procedures live in .agents/skills/. Tool wiring lives in
.mcp.json. Product, feature, and human-input contracts live in .agents/contracts/.
Safe runtime coordination lives under gitignored .agent-state/; credentials never do.
The project-scoped agentic-ship MCP server wraps the real health, verification,
connection, queue, and UI-evidence services. Its mutation tools require the explicit
--allow-mutations server argument; its full contract lives in
.agents/skills/agent-compatibility/references/agentic-ship-mcp.md.
Plugin wiring lives in .claude/settings.json (the official nextjs plugin from the
vercel/next.js repo is declared there). Provenance for all of it lives in
skills.lock.json. One rule, one home: it is declared here, applied there.
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 · 726 lines · 11,608 tokens per session scan C 38bcd2a13f76
agentic-ship AGENTS.md is an instructions file published in the GitHub repository moasq/agentic-ship (10 stars, last pushed 4d ago), licensed MIT. It adds 11,608 tokens to every session, about $0.0580 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
open-supermarkets AGENTS.md
Instructions for abracadabra50/open-supermarkets, covering agent integration guide, supported frameworks, quick integration, 1. add as skill and 2. agent calls commands.
helm copilot-instructions.md
Instructions for PetePeter/helm, covering gamepad-cli-hub — copilot instructions, project purpose, system overview, data flow pipeline and key controls.
fusion-skills AGENTS.md
AGENTS.md instructions for CrowdStrike/fusion-skills, covering agents.md, what this is, prerequisites, repository structure and skills ecosystem.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.