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.
npx skills add eagerworks/skills --skill repo-handoffgit clone --depth 1 https://github.com/eagerworks/skillsWrote 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/skills/eagerworks/skills/repo-handoff)<a href="https://agentmods.dev/skills/eagerworks/skills/repo-handoff"><img src="https://agentmods.dev/badge/skills/eagerworks/skills/repo-handoff/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/skills/eagerworks/skills/repo-handoff"><img src="https://agentmods.dev/badge/skills/eagerworks/skills/repo-handoff.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.00142 | $0.02197 |
| Opus 5.5 | $0.00057 | $0.00879 |
| Sonnet 5.5 | $0.00028 | $0.00439 |
| Haiku 4.5 | $0.00014 | $0.00220 |
Grade A, and why
repo-handoff 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 1mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Handoff Skill
A handoff is the moment a codebase changes hands: one team stops owning it, another starts. Most of what the outgoing team knows is not in the repo — which account owns the DNS, why that migration was never run, which cron job must not overlap, who gets paged. This skill reads the repo from the receiving team's point of view, records everything the code does answer, and turns everything it doesn't into a concrete, prioritized list of questions for the previous team — so the knowledge-transfer meeting is spent on the real gaps, not on things grep could have told you.
The analysis is read-only with exactly one write: the finished report is printed in chat and saved to docs/repo-handoff.md at the analyzed repo's root (docs/ is created if missing; the file is overwritten on re-run, preserving answers already filled in). Nothing else is created, edited, committed, or pushed.
Discovery — Do This First
Classify the project before analyzing anything. Every check in references/dimensions.md depends on knowing the stack and where things live.
1. Detect the stack(s) from manifests at the root and in workspace globs (package.json#workspaces, pnpm-workspace.yaml, turbo.json, Gemfile in subdirs, pyproject.toml, go.mod, *.csproj, pubspec.yaml, app.json/eas.json).
2. Inventory the written knowledge — read in full, don't skim: README*, CONTRIBUTING*, docs/**, AGENTS.md, CLAUDE.md, CHANGELOG*, ADRs, wikis checked into the repo, .env.example, docker-compose*.yml, Dockerfile*, .github/**, .gitlab-ci.yml, config/deploy*, terraform/, infra/, Procfile, fly.toml, render.yaml, vercel.json, app.yaml.
3. Mine the history — git log, git shortlog -sn, git branch -a, tags, open PRs/issues via gh if available. Authorship concentration, last-activity dates, and unmerged branches are the handoff's early-warning signals.
4. Enumerate every external touchpoint — anything the code talks to that lives outside the repo: databases, queues, SaaS APIs, payment providers, email/SMS, auth providers, object storage, CDNs, analytics, error tracking, app stores, domains. Each one is an account someone owns and a credential someone holds — the two things most often lost in a handoff.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 92 lines · 142 tokens per session scan A db41e5d947a2
repo-handoff is a skill published in the GitHub repository eagerworks/skills (14 stars, last pushed 1mo ago), licensed MIT. It adds 142 tokens to every session and 2,197 once invoked, about $0.0006 per session on Opus 5.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-09-13.
Other skills, from other repositories
careers-page-generator
Deprecated compatibility entry for Careers Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Careers Page.
changelog-page-generator
Deprecated compatibility entry for Changelog Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Changelog Page.
feedback-page-generator
Deprecated compatibility entry for Feedback Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Feedback Page.
status-page-generator
Deprecated compatibility entry for Status Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Status Page.
os-big-picture
ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what does this thing even do", "what is stale", "what can we delete", "update the roadmap" - in any language, and whenever a…
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use…