Borrowing it
Nothing to install: this file belongs to jonthebeef/deckhand. 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/jonthebeef/deckhand/main/CLAUDE.mdgit clone --depth 1 https://github.com/jonthebeef/deckhandWrote 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/jonthebeef/deckhand/claude-md)<a href="https://agentmods.dev/instructions/jonthebeef/deckhand/claude-md"><img src="https://agentmods.dev/badge/instructions/jonthebeef/deckhand/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/jonthebeef/deckhand/claude-md"><img src="https://agentmods.dev/badge/instructions/jonthebeef/deckhand/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00765 | $0.00765 |
| Opus 5.5 | $0.00306 | $0.00306 |
| Sonnet 5.5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
deckhand CLAUDE.md scanned grade A 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
A Claude Code **plugin** bundling two skills, `ticket-lifecycle` and `managing-project-backlog`. The same skills also run standalone on Codex and Cursor, so keep everything platform-agnostic (plain Markdown plus `gh` / ` How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deckhand
A Claude Code plugin bundling two skills, ticket-lifecycle and managing-project-backlog. The same skills also run standalone on Codex and Cursor, so keep everything platform-agnostic (plain Markdown plus gh / curl, no Claude-Code-only hooks).
Layout
.claude-plugin/plugin.json- the plugin manifest (name, version, license, etc.). Only this file lives in.claude-plugin/.skills/ticket-lifecycle/andskills/managing-project-backlog/- the two skills, each aSKILL.mdplus supporting files. Skills live atskills/<name>/, not inside.claude-plugin/.- Root:
VERSION,bump.sh,README.md,CHANGELOG.md,CLAUDE.md,LICENSE.
Versioning and releases
- The version lives in four places, kept in sync: the root
VERSION,skills/ticket-lifecycle/VERSION,skills/managing-project-backlog/VERSION, and theversionfield in.claude-plugin/plugin.json. They share a single number. - Do not edit those by hand. Use the helper:
./bump.sh patch | minor | major(or./bump.sh X.Y.Z). It writes all four and prints the publish commands. - Bump whenever you ship a user-facing change to either skill: patch for fixes, minor for new behaviour, major for breaking changes. Add a
CHANGELOG.mdentry too. - A change is not "released" until the bump is on
main. That triggers the standalone-skills update offer, and the plugin manager picks up the newplugin.jsonversion. The check compares version strings, so the published number must only ever go up.
How updates reach users
- Each skill's first-invocation protocol runs a throttled (once / 24h), opt-out version check and offers an update only when the local copy is behind. Stay-quiet-otherwise is the intended behaviour.
- Updates are agent-driven and applied in place. They MUST preserve the user's populated
board-config.md(it holds their real board IDs). If you ever touch the update or check instructions, keep that preservation rule intact and keep it working the same on Claude Code, Codex, and Cursor.
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.
- 2mo ago First seen · 31 lines · 765 tokens per session scan A 0b7e4d89645a
deckhand CLAUDE.md is an instructions file published in the GitHub repository jonthebeef/deckhand (6 stars, last pushed 3mo ago), licensed MIT. It adds 765 tokens to every session, about $0.0031 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.