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.
curl -O https://raw.githubusercontent.com/moviendome/Shippy/main/CLAUDE.mdgit clone --depth 1 https://github.com/moviendome/ShippyWrote 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/moviendome/shippy/claude-md)<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>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.00410 | $0.00410 |
| Opus 5 | $0.00205 | $0.00205 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
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.
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_USERNAMEin.env(GitHub collaborator on target repos) - Runtime dir:
~/shippy/on VPS (not in git — contains.env, logs, state) - Lock: Both workers share
~/shippy/.lockviaflockfor mutual exclusion - Notifications: Telegram bot posts to a group chat
Conventions
- All scripts use
set -euo pipefail - Source lives in
agents/, deployed to~/shippy/viabin/deploy .envfiles are runtime-only, never committed- Brainstorms go in
docs/brainstorms/, plans indocs/plans/ - jq: use
(.x == $y | not)instead of.x != $y(bash history expansion bug)
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.
- 7d ago First seen · 39 lines · 410 tokens per session scan A f73a49df65d8
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.
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.
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).
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.
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).
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.