Borrowing it
Nothing to install: this file belongs to yongjip/mergetrain. 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/yongjip/mergetrain/main/CLAUDE.mdgit clone --depth 1 https://github.com/yongjip/mergetrainWrote 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/yongjip/mergetrain/claude-md)<a href="https://agentmods.dev/instructions/yongjip/mergetrain/claude-md"><img src="https://agentmods.dev/badge/instructions/yongjip/mergetrain/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.01218 | $0.01218 |
| Opus 5 | $0.00609 | $0.00609 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
mergetrain 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 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.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — operating mergetrain from Dispatch
This repository ships mergetrain, a local deploy train for coding-agent worktrees. Keep phone-facing results short and actionable. Setup and phrasebook details live in docs/mobile.md.
Shared operating protocol
Purpose: Serialize committed local task branches through one merge/test/push/verify runner.
Existing queues and explanations
- Existing mergetrain repositories keep status → enqueue → stop even for one branch. Queue counts alone do not establish health, runner ownership, or recovery needs; read
health,state, andnext_actiontogether. - For explanation-only requests, read the skill documentation when permitted and explain the procedure without Git or product commands. Distinguish hypothetical steps from observed state.
Current command reference
- The v3 core commands are
init,status,enqueue,validate,deploy, andinspect. - Start with
mergetrain status --json. Usemergetrain status --diagnose --jsononly for configuration, Git, runtime, or lock detail, andmergetrain inspect JOB_ID --jsonfor job evidence.doctoris removed, not an alias forstatus --diagnose. - Confirm uncertain syntax with the installed
mergetrain --versionand command-specific--helponly when command execution is permitted. Otherwise use this reference and identify missing details; do not invent commands or copy older syntax from unversioned web results. Inspection andnext_actiondo not authorize recovery or deployment.
Rules
- Work on a task-specific branch and worktree.
- Commit a clean HEAD before handing work off.
- Read mergetrain status --json and follow its next action before changing queue state.
- Enqueue every named finished branch in the requested order using only its task and branch; mergetrain resolves the worktree and captures the exact commits. Stop after the last successful enqueue unless the user explicitly authorized validation or the complete validation-and-deployment workflow.
- Never push configured integration refs directly. One authorized runner owns validation and deployment; recovery and destructive actions require their stated approval.
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 Changed · +12 lines · +309 tokens per session aeb819c3e3b8
- 3d ago Changed · -6 lines · -785 tokens per session cbfe1d52b1c1
- 7d ago First seen · 105 lines · 1,694 tokens per session scan A 88ca57de0f9e
mergetrain CLAUDE.md is an instructions file published in the GitHub repository yongjip/mergetrain (3 stars, last pushed 2d ago), licensed MIT. It adds 1,218 tokens to every session, about $0.0061 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.