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/wrap-session/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/wrap-session)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/wrap-session"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/wrap-session/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/wrap-session"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/wrap-session.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.00847 |
| Opus 5.5 | $0.00017 | $0.00339 |
| Sonnet 5.5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
wrap-session 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap session
A wrap transfers completed work and remaining state to the repository's declared owners. It is not a generic requirement to create issues, edit changelogs, or push commits in every project.
1. Confirm this is a wrap point
Wrap when the thread is finished, the user asks to wrap, or an authorized merge
finishes the thread. Do not wrap an unfinished task; use context-handoff when
context is running out mid-task.
A merged stage in a tightly coupled staged set may refresh continuity and then continue in-session. The discriminator is whether the thread is finished, not whether a commit or PR exists.
2. Read the repository declaration
Read the repository declaration (the AGENTS.md chain) and identify:
- task tracker and completion state;
- handoff form, if any;
- changelog policy;
- memory policy;
- remote persistence and merge rules;
- authorization for every external write.
Where no surface is declared, skip it. Never create a GitHub handoff beside a declared handoff file or vice versa.
3. Verify accumulated status
Use evidence collected during the session and refresh only the state that can have changed:
git status --short
git log --oneline -5
When GitHub is in use, read back the relevant PR and issue state. Distinguish:
- committed, pushed, merged, and deployed;
- passing tests from tests not run;
- verified facts from assumptions;
- current-session changes from pre-existing worktree changes.
Do not sweep unrelated changes into the wrap.
4. Update each declared owner once
Apply the carrier rule:
| Fact | Owner |
|---|---|
| shipped change | declared changelog |
| architecture decision | ADR, plan, or decisions log |
| gotcha or hard-won reason | auto-memory |
| convention or procedure | repository docs |
| remaining task or decision | declared tracker |
| commit history | git |
For a completed issue, let Closes #N or Fixes #N close it on merge when that
is the repository convention. Remove an in-progress marker only after confirming
the task is complete. A partially advanced issue stays open with a concise
progress update.
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 · 115 lines · 43 tokens per session scan A 5766b1bcac75
wrap-session 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 847 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…