What is legacy-project-handover?

A read-only briefing process for understanding an existing codebase and handing it over to another developer or agent. It reconstructs the current state from project files, documentation, and version history.

Use it when starting a new session, taking over a project, recovering after losing context, or preparing a concise project snapshot before making changes.

It reduces the time needed to understand unfamiliar work and lowers the risk of relying on outdated or informal explanations. It does not change the repository.

legacy-project-handover — Skill for Claude Code and Codex by blackzhan

Install

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.

Any agent

npx skills add blackzhanzhan/Cyber-Ming-Protocol --skill legacy-project-handover

Clone the repo

git clone --depth 1 https://github.com/blackzhanzhan/Cyber-Ming-Protocol

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/blackzhanzhan/cyber-ming-protocol/legacy-project-handover/github.svg)](https://agentmods.dev/skills/blackzhanzhan/cyber-ming-protocol/legacy-project-handover)

Your own site

<a href="https://agentmods.dev/skills/blackzhanzhan/cyber-ming-protocol/legacy-project-handover"><img src="https://agentmods.dev/badge/skills/blackzhanzhan/cyber-ming-protocol/legacy-project-handover/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/blackzhanzhan/cyber-ming-protocol/legacy-project-handover"><img src="https://agentmods.dev/badge/skills/blackzhanzhan/cyber-ming-protocol/legacy-project-handover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,263 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00053	$0.01263
Opus 5	$0.00026	$0.00632
Sonnet 5	$0.00011	$0.00253
Haiku 4.5	$0.00005	$0.00126

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

Security

Grade A, and why

legacy-project-handover 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 11d 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.

skill/legacy-project-handover/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Succession Brief

Compatibility note: the skill keeps the historical name legacy-project-handover, but its intended role is broader. It serves as a fresh-session brief, a succession snapshot after context decay, and a read-only handover summary before implementation begins.

Prerequisite: read and obey the repository parent policy at skill/global_rules/SKILL.md first.

Responsibility

This skill is read-only.
It is for current-state reconstruction, not implementation.
It is especially suited for:
- fresh-session recovery
- succession after context decay
- takeover before edits
- concise project snapshot generation

Read-Only Red Line

Do not propose code edits.
Do not call any file-writing or file-editing tool.
Do not drift into broad research beyond what is needed to reconstruct the present state.

Workflow

If dev_repo/state.json and dev_repo/tree.md exist, read them first as the current process truth.
If dev_repo/architecture/ exists, read README.md, ARCHITECTURE.md, graph.json, index.json, and invariants.md before relying on oral or README-level architecture claims.
If dev_repo/architecture/data-model/ exists, read README.md, ER.md, entities.json, relationships.json, and invariants.md before relying on oral or README-level data claims.
If dev_repo/architecture/ does not exist and the user is taking over an old project, mark architecture_census_required as the first implementation precondition. Do not pretend a project can be planned safely from process truth alone.
If durable data semantics exist but dev_repo/architecture/data-model/ does not exist, mark data_model_census_required as the first implementation precondition before broad data-changing work.
Read the most recent 10-30 commits and cluster them by engineering theme.
Read the core architecture, data-model, and process documents actually governing the current project state.
Inspect only the mainline code paths needed to understand current delivery status, architecture shape, and durable data shape.
Produce a short brief using headings in the user's working language. Use Stage, Completed, Architecture, Bottleneck, Next Step for English users, or 阶段, 已完成, 架构, 瓶颈, 下一步 for Chinese users.

Read the full file on GitHub · 98 lines

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.

11d ago First seen · 98 lines · 53 tokens per session scan A 9b1f4fa9400e

Subscribe to this mod's changes

legacy-project-handover is a skill published in the GitHub repository blackzhanzhan/Cyber-Ming-Protocol (56 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,263 once invoked, about $0.0003 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-30.

Project management Writing and docs agent-governance agent-workflow ai-agent ai-coding developer-tools

legacy-project-handover

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Succession Brief

Responsibility

Read-Only Red Line

Workflow

What this file has done since we first saw it

Other skills, from other repositories

issue-creation

sdd-tasks

systemic-issue-triage

workspace

ticket-craft

team-coordination