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 photostructure/coding-skills --skill handoffgit clone --depth 1 https://github.com/photostructure/coding-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/photostructure/coding-skills/handoff)<a href="https://agentmods.dev/skills/photostructure/coding-skills/handoff"><img src="https://agentmods.dev/badge/skills/photostructure/coding-skills/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/photostructure/coding-skills/handoff"><img src="https://agentmods.dev/badge/skills/photostructure/coding-skills/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.00032 | $0.00435 |
| Opus 5.5 | $0.00013 | $0.00174 |
| Sonnet 5.5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
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.
What it actually says
TPP Handoff
Documented in depth: Claude Code has amnesia. So do PRs, changelogs, and your future self.
We're out of time and need to hand off the remaining work. The Technical Project Plan (TPP) is the handoff document — whatever this session learned must end up in the file, or the next session re-learns it the hard way.
Required Reading First
Before any work, you MUST read:
- The project's instructions:
AGENTS.md, plusCLAUDE.mdwhen present - The project's TPP guide:
docs/TPP-GUIDE.mdif it exists; otherwise the bundled reference TPP-GUIDE.md
Your Task
Apply the guide's Handoff rules and Keeping TPPs useful sections to the active TPP. What this session learned that the repository does not already record — gotchas, dead ends and why they failed, the reasoning behind decisions — is the part that must end up in the file.
The bar: the next session should be able to invoke the tpp skill with the plan
path and continue without asking what happened last time.
Adapting for your project
- Extend the required reading list with the same project docs your
tppskill reads — the two skills should share one list. - Set the trimming and focus rules in your project's
docs/TPP-GUIDE.md, which owns them. Don't reintroduce a line budget here — the guide deliberately measures focus, not length.
What ships with it
1 file 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 · 41 lines · 32 tokens per session scan A e42b7aff3914
handoff is a skill published in the GitHub repository photostructure/coding-skills (4 stars, last pushed 21d ago), licensed MIT. It adds 32 tokens to every session and 435 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…