Borrowing it
Nothing to install: this file belongs to vladm3105/aidoc-flow-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vladm3105/aidoc-flow-framework/dev/.agents/skills/context-handoff/SKILL.mdgit clone --depth 1 https://github.com/vladm3105/aidoc-flow-frameworkWrote 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/vladm3105/aidoc-flow-framework/context-handoff)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/context-handoff"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/context-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/vladm3105/aidoc-flow-framework/context-handoff"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/context-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.00043 | $0.00520 |
| Opus 5.5 | $0.00017 | $0.00208 |
| Sonnet 5.5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
context-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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context handoff
Use this only when both conditions hold: the task is unfinished and context is
about to end. A finished thread uses wrap-session; an unfinished task with
enough context keeps going.
1. Read the repository declaration
Identify the active task surface, handoff policy, remote persistence rules, and authorization for comments, commits, and pushes. Do not assume every repository uses GitHub issues or permits autonomous remote writes.
2. Capture durable findings first
Route each actionable defect or improvement through submit-feedback before
writing resume state. A task-scoped note dies when the task finishes and is not
a durable defect tracker.
3. Record resumable task state
Use the repository's declared in-progress work item. Prefer a comment on the active issue when GitHub is authorized; otherwise use its declared WIP or local handoff mechanism. Do not edit the session handoff unless the repository says it also owns mid-task state.
The resume record contains:
## Resume state — YYYY-MM-DD, context boundary
- Done and verified: <work plus verification>
- Done, not verified: <remaining checks>
- In flight: <files and partial state>
- Not started: <remaining scope>
- Next action: <one action requiring no rediscovery>
- Blockers: <reason and clearing condition>
- Assumptions: <each unverified claim>
When posting a GitHub comment, use --body-file - and read the comment back.
Writing to an external tracker requires repository or user authorization.
4. Preserve the work
If changes are uncommitted, state that plainly. Commit or push a WIP checkpoint
only when requested or authorized by repository policy. Never use git add -A
without first separating pre-existing changes from the current task.
When a push is authorized, verify the intended remote contains the checkpoint; a local commit or successful command is not proof of persistence.
5. Report
Return the work-item identifier or local record path, read-back or persistence evidence, remaining uncommitted state, and the exact next action. State that this was a context handoff, not a wrap: the task remains open and nothing was closed.
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 · 63 lines · 43 tokens per session scan A a6c0386cd6eb
context-handoff is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 520 once invoked, about $0.0002 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-09-28.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.