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 handoff-promptgit 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-prompt)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/handoff-prompt"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/handoff-prompt/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-prompt"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/handoff-prompt.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.00061 | $0.00514 |
| Opus 5 | $0.00030 | $0.00257 |
| Sonnet 5 | $0.00012 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
handoff-prompt 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.
What it actually says
handoff-prompt
Handoff plus kickoff prompt — use when a wave closes and the next session needs a paste-ready driver.
Output (always both)
- Handoff doc —
handofftemplate; save to:adam/memory/handoffs/<topic>-<YYYY-MM-DD>.md(harness-level)scratch/handoff/handoff-<YYYYMMDD-HHmm>.md(product repo)
- Kickoff prompt file —
scratch/handoff/KICKOFF-<topic>.mdwith the full paste-ready orchestrator prompt (not a summary). - Chat block — print kickoff prompt in a fenced code block for copy/paste.
Kickoff prompt sources
agent-control/next-orchestrator-brief.md(canonical in product repos)orchestrate-builddriver preambleplan/ORCHESTRATOR.mdif the repo defines one- Branch rules from
foundation/repo/folder-contract.md(adam/<slice-id>)
Include: mission, read-first paths, slice scope, stop conditions, operator gates.
Cross-workspace continuation
No API spawns a fresh agent chat in another repo with a preloaded prompt. Options:
| Mode | What happens |
|---|---|
| A — Copy/paste (default) | New chat in target repo; @ handoff + KICKOFF; paste prompt |
| B — Same chat switch | User approves → cursor-app-control move_agent_to_root → continue kickoff here |
| C — Multi-root | move_agent_to_root with rootPaths: [harness, product-repo] |
Do not call move_agent_to_root without explicit user approval.
Quality bar
- Handoff under 150 lines; kickoff may be long.
- Next concrete step at top of both files.
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 · 45 lines · 61 tokens per session scan A 70a6c14c50a1
handoff-prompt is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 61 tokens to every session and 514 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…