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.
/plugin marketplace add jasonm4130/claude-skillsnpx agentmods add plugins/jasonm4130/claude-skills/handoffgit clone --depth 1 https://github.com/jasonm4130/claude-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/plugins/jasonm4130/claude-skills/handoff)<a href="https://agentmods.dev/plugins/jasonm4130/claude-skills/handoff"><img src="https://agentmods.dev/badge/plugins/jasonm4130/claude-skills/handoff.svg" alt="Measured on agentmods" height="20"></a>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 5d 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
{
"name": "handoff",
"description": "Manual /handoff skill — writes a structured resume doc on demand, auto-loads it on next session.",
"version": "0.11.1",
"author": {
"name": "Jason Matthew"
},
"homepage": "https://github.com/jasonm4130/claude-skills",
"repository": "https://github.com/jasonm4130/claude-skills",
"license": "MIT",
"keywords": [
"handoff",
"context",
"resume",
"session-continuity",
"claude-code"
],
"engines": {
"claude-code": ">=2.1.110"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 130 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago First seen · 22 lines scan A deb51be52c53
handoff is a plugin published in the GitHub repository jasonm4130/claude-skills (5 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-code-plugin
Lossless context compression for Claude Code.
fuse-lessons
Project memory: writes compact 'never reproduce' lessons to MEMORY/LESSON.md on finish, force-reads them at session/subagent start.
neatcontext marketplace
Save Claude Code work as reusable, domain-aware context.
neatcontext
Save Claude Code work as reusable, domain-aware context.
mf
mindfunnel — project-agnostic Claude Code session management. Five slash-command skills: /mf:setup seeds /.mindfunnel/ (AGENTS, SOUL, USER, PROJECT templates) and the /.claude/ + /.codex/ symlinks to the user-global personal files; /mf:prime stamps a committed project-scoped AGENTS.md + intra-repo CLAUDE.md symlink.
heading-core
Sovereignty and session core: the prime/state-check/checkpoint skills, the standalone sovereignty guard hooks, and the session checkpoint system - a context-usage sensor, a threshold offer, a pre-compaction brief that states what the summary must keep verbatim, a redacted post-compact save, and a resume injector, all…