Shippy: Instructions file for Claude Code

CLAUDE.md

Shippy CLAUDE.md is an instructions file for Claude Code from moviendome/Shippy. It costs 410 tokens per session, scanned A, original, MIT.

A set of instructions for Shippy, an autonomous GitHub agent that takes assigned issues and creates pull requests. It also describes a worker that processes review feedback when the agent is mentioned on a pull request.

In plain words
What is it for?
It is for developers working on Shippy’s issue worker, feedback worker, deployment scripts, configuration, logs, and state files.
Why use it?
It explains how the automated workers, repository layout, GitHub account, runtime files, and shared lock are organised. This reduces guesswork when operating or maintaining Shippy.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is moviendome/Shippy's own configuration. It tells Claude Code how to work on Shippy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Shippy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to moviendome/Shippy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/moviendome/Shippy/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/moviendome/Shippy

Made for: Claude Code.

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

agentmods badge for Shippy CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/moviendome/shippy/claude-md.svg)](https://agentmods.dev/instructions/moviendome/shippy/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/moviendome/shippy/claude-md"><img src="https://agentmods.dev/badge/instructions/moviendome/shippy/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 410 This file is loaded in full into every session.
When invoked 410 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00410 $0.00410
Opus 5 $0.00205 $0.00205
Sonnet 5 $0.00082 $0.00082
Haiku 4.5 $0.00041 $0.00041

Measured 7d ago against content hash f73a49df65d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

Shippy CLAUDE.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 7d 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.

CLAUDE.md · 39 lines

What it actually says

CLAUDE.md

Shippy is an autonomous GitHub agent that ships PRs from assigned issues.

Repo Structure

agents/
  issue-worker.sh              # Picks up assigned GitHub issues, creates PRs
  issue-worker-prompt.md       # System prompt for issue worker
  feedback-worker.sh           # Processes @mention feedback on PRs
  feedback-worker-prompt.md    # System prompt for feedback worker
bin/
  deploy                       # Deploy agents to ~/shippy/ on VPS
docs/
  brainstorms/                 # Brainstorming sessions
  plans/                       # Implementation plans

How It Works

  • Issue Worker: Runs on schedule via cron. Finds GitHub issues assigned to the agent account across all repos using GitHub search API. Creates a worktree, runs Claude Code with /workflows:work, and opens a PR.
  • Feedback Worker: Runs every 5 minutes via cron. Polls for @mentions on Shippy PRs, processes review feedback with Claude Code, pushes fixes.

Key Details

  • Agent account: Set via AGENT_GITHUB_USERNAME in .env (GitHub collaborator on target repos)
  • Runtime dir: ~/shippy/ on VPS (not in git — contains .env, logs, state)
  • Lock: Both workers share ~/shippy/.lock via flock for mutual exclusion
  • Notifications: Telegram bot posts to a group chat

Conventions

  • All scripts use set -euo pipefail
  • Source lives in agents/, deployed to ~/shippy/ via bin/deploy
  • .env files are runtime-only, never committed
  • Brainstorms go in docs/brainstorms/, plans in docs/plans/
  • jq: use (.x == $y | not) instead of .x != $y (bash history expansion bug)
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. 7d ago First seen · 39 lines · 410 tokens per session scan A f73a49df65d8

Subscribe to this mod's changes

Shippy CLAUDE.md is an instructions file published in the GitHub repository moviendome/Shippy (2 stars, last pushed 6mo ago), licensed MIT. It adds 410 tokens to every session, about $0.0020 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-31.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

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

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens