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 Justinmendezai/The-Adam-Repo --skill handoffgit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/justinmendezai/the-adam-repo/handoff)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/handoff"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-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/justinmendezai/the-adam-repo/handoff"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.01448 |
| Opus 5 | $0.00029 | $0.00724 |
| Sonnet 5 | $0.00012 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
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 12d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
handoff
Adapted from Matt Pocock's handoff. General-purpose conversational handoff. For Adam factory builds, prefer context-primer which understands the loop's state.
When to use
- Switching from one agent to another mid-task (e.g. moving to a fresh Cursor chat).
- The current conversation is too long to be efficient and you want to start fresh without losing state.
- Wrapping for the day on an in-progress task.
Output
A handoff doc on disk and a kickoff block in chat. The doc is for the next agent; the chat block is for the operator to copy into a fresh session.
Handoff doc template
# Handoff — <short title>
- From: <agent + user>
- Date: <ISO timestamp>
- Repo: <absolute path>
## What we're doing
One paragraph.
## What we've done
Bulleted, terse:
- Decided X
- Implemented Y (link/path)
- Tested Z
## What's next
The single concrete next step. Be specific about commands or skills to invoke.
## Open questions
Bulleted. Things we deferred.
## Files the next agent should read
1. <path>
2. <path>
3. foundation/repo/agent-control/standing-operator-rules.md *(Adam factory loops — always)*
## Files the next agent should NOT re-read
The full transcript of this conversation.
Long source files unless the next step requires them.
## Quirks / gotchas
- Up to 3 bullets. Stuff that bit us.
Workflow
- Skim the conversation. Identify decisions, completed work, open threads.
- Resolve absolute repo path (workspace root /
tech_context.repo_path/pwd). If multi-repo, pick the one the next agent must open first. - Fill the template above. Include
Repo:in the doc header. - Save to
handoff-<YYYYMMDD-HHmm>.mdin the working directory (orscratch/handoff/for an Adam factory flow). - Required chat closing — do not end with only a file path. In the same assistant message, output all of:
Required chat closing (mandatory)
In the same assistant message, include:
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.
- 12d ago First seen · 143 lines · 58 tokens per session scan A 68dbe4b2e8a3
handoff is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,448 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…