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 avizmarlon/agent-skills --skill multi-phase-sessiongit clone --depth 1 https://github.com/avizmarlon/agent-skillsWrote 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/avizmarlon/agent-skills/multi-phase-session)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/multi-phase-session"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/multi-phase-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/avizmarlon/agent-skills/multi-phase-session"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/multi-phase-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.01711 |
| Opus 5.5 | $0.00017 | $0.00684 |
| Sonnet 5.5 | $0.00009 | $0.00342 |
| Haiku 4.5 | $0.00004 | $0.00171 |
Grade A, and why
multi-phase-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 2mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Phase Session Management
Large software projects, long-term initiatives, or phased work—where each phase is a distinct milestone with clear acceptance criteria—benefit from a session-per-phase model instead of trying to compact context within a single conversation.
Why separate sessions per phase
AI context quality degrades measurably around 60% of capacity (before auto-compact), and subsequent compacts introduce truncation and lossy summarization. A project split across multiple compact cycles accumulates error.
Better pattern:
- One AI session per phase
- Each phase terminates with a commit, updated handoff, and session closure
- Next phase opens fresh with the handoff file and project docs as context source
- The codebase, specification documents, and handoff file are the canonical context—not the previous chat history
This preserves quality because:
- The next agent (or next session with the same agent) reads living docs, not truncated chat summaries
- Decisions, blocked items, and state are recorded in files meant for future readers, not buried in chat
- Each phase is independently validated before moving forward
- Context isn't split across a "what I remember from chat" and "what the files say"
Session lifecycle per phase
Phase completion checklist
Before closing a session:
- Code is committed — all work merged to the appropriate branch or merged to main (per project CI rules)
- Acceptance criteria are met — the phase has a defined "done" state; validate it
- Handoff is written/updated — if the project uses
session-handoff.mdor equivalent, it reflects current state - Next phase is clear — the handoff names the next objective, expected duration, and any blockers
- CHANGELOG or progress log is updated — significant milestones are recorded for future reference
Opening a new session for the next phase
- Read the handoff first — open
session-handoff.mdor equivalent in full before proceeding - Check git state —
git status,git branch,git log --oneline -5to understand current state - Verify acceptance criteria from prior phase — confirm the last phase actually completed and is clean
- Read critical docs — specification, architecture decisions (ADRs), any phase-specific README
- Begin with verification — first steps validate the prior phase is stable before building the next one
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.
- 2mo ago First seen · 131 lines · 43 tokens per session scan A 9a8a54383fc6
multi-phase-session is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,711 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-08-31.
Other skills, from other repositories
apple-reminders
Apple Reminders via remindctl: add, list, complete.
apple-notes
Manage Apple Notes via memo CLI: create, search, edit.
box
Box manages cloud files, sharing, search, and metadata.
obsidian
Read, search, create, and edit notes in the Obsidian vault.
channels-setup
Use when a developer wants to build their first CopilotKit Channels agent and get it answering in Slack or Microsoft Teams: "set up a channel", "connect my agent to Slack", "get my agent into Teams", or starting from nothing and wanting a working channel end to end. Covers the whole path: inspecting or scaffolding the…
mantis-configure
Configures and validates Mantis pipeline environments, sandbox mechanisms, and AI models. Use to set up workflow.json, auto-detect host capabilities, switch between sandboxes (static-only, gvisor, microsandbox, gce), select AI models, and run fast 1-2s preflight tests. Don't use for scanning source code or running…