Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add OneDro1d/dark-factory/plugin install agent-notepadWrote 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/onedro1d/dark-factory/handoff)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/handoff"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/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/onedro1d/dark-factory/handoff"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/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.00206 | $0.02242 |
| Opus 5 | $0.00103 | $0.01121 |
| Sonnet 5 | $0.00041 | $0.00448 |
| Haiku 4.5 | $0.00021 | $0.00224 |
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 4d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
handoff — publish a deliberate Handoff doc into the notepad
Notes vs Handoff — the terminology split (read first)
agent-notepad keeps working memory in two tiers, and this skill owns only the second:
- Notes — the continuous tier.
NOTES.md(compact, rewritten in place) plus the append-only journal (sessions/<ISO8601>_<id>.jsonl). Kept fresh automatically by the Stop / PreCompact / UserPromptSubmit hooks and auto-loaded every SessionStart. You do not invoke a skill for Notes — they just accrue. - Handoff — the deliberate tier. A single structured document you publish on
demand at a meaningful boundary (milestone, teammate hand-off, end of a work block).
This is what
/handoffproduces.
A Handoff summarizes the current Notes into a durable, shareable artifact; it does not replace them. Notes are the stream; a Handoff is a snapshot you deliberately cut and push. When in doubt: routine progress → let the Notes hooks capture it; a real checkpoint someone else (or a fresh you) will read cold → publish a Handoff.
What this does
-
Resolves the active notepad (nearest ancestor of cwd with
NOTES.md). -
Writes the structured handoff to
<notepad>/handoffs/<date>-<topic>.md— inside the notepad, never the OS temp dir — so it is versioned and syncs. -
Redacts secrets (API keys, tokens, bearer/JWT, private keys,
password=…). -
References artifacts by path or URL (PRDs, plans, ADRs, commits, diffs, per-repo
df-context-storefindings) instead of duplicating their content. -
Suggests next skills the receiving agent should invoke.
-
Forces a
git pushof the notepad (git add → commit → push, best-effort) so the -
⚠️ Update
NOTES.mdyourself, and commit it WITH the handoff. Operator rule, 2026-07-29: "Commit the handoff together with the session's NOTES.md update and any deploy-evidence, so the checkpoint is one coherent commit."⛔ This is not bookkeeping — it is the only thing that makes the handoff reachable.
session-start.shinjectsNOTES.md,DIGEST.mdandrepos.manifest.json; it does not readhandoffs/. A handoff published without a Notes update is invisible to every cold session — and the restore that misses it looks completely healthy.
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.
- 4d ago Changed · +13 lines · +62 tokens per session 44121c50c9b6
- 6d ago Changed · +34 lines 2d7c32de4b45
- 9d ago First seen · 99 lines · 144 tokens per session scan A 70bd33bd7eb7
handoff is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 206 tokens to every session and 2,242 once invoked, about $0.0010 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-09-01.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…