waypoint:workflow

waypoint:workflow is a skill for Claude Code from aeriondyseti/vector-memory-mcp. It costs 90 tokens per session (1,567 once invoked), scanned A, original, MIT.

A workflow for saving and restoring a structured snapshot of a coding session. A waypoint records completed work, decisions, unfinished items, and next steps.

In plain words
What is it for?
Use it after finishing a task, before clearing context, or when switching tasks and needing a clear point to continue from.
Why use it?
It prevents important project context from being lost when a session is cleared or resumed later.

Skill for Claude Code

Written for Claude Code: SessionStart hook event.

Part of the vector-memory plugin — 4 skills, 3 hooks, 1 MCP server shipped together

Good fit Use it after finishing a task, before clearing context, or when switching tasks and needing a clear point to continue from.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aeriondyseti/vector-memory-mcp/waypoint-workflow
Install

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.

Any agent
npx skills add aeriondyseti/vector-memory-mcp --skill waypoint-workflow
Clone the repo
git clone --depth 1 https://github.com/aeriondyseti/vector-memory-mcp

Made for: Claude Code.

Or install vector-memory, the plugin that ships this one along with the rest of its 4 skills, 3 hooks, 1 MCP server.

Wrote 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.

agentmods badge for waypoint:workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/aeriondyseti/vector-memory-mcp/waypoint-workflow/github.svg)](https://agentmods.dev/skills/aeriondyseti/vector-memory-mcp/waypoint-workflow)
Your own site
<a href="https://agentmods.dev/skills/aeriondyseti/vector-memory-mcp/waypoint-workflow"><img src="https://agentmods.dev/badge/skills/aeriondyseti/vector-memory-mcp/waypoint-workflow/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.

agentmods 80×15 button for waypoint:workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/aeriondyseti/vector-memory-mcp/waypoint-workflow"><img src="https://agentmods.dev/badge/skills/aeriondyseti/vector-memory-mcp/waypoint-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,567 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00090 $0.01567
Opus 5 $0.00045 $0.00783
Sonnet 5 $0.00018 $0.00313
Haiku 4.5 $0.00009 $0.00157

Measured 9d ago against content hash 950ca4d6f41a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

waypoint:workflow 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 9d 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.

plugin/skills/waypoint-workflow/SKILL.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Waypoint Workflow

Waypoints capture a structured snapshot of session state — what was accomplished, what decisions were made, and what comes next. They enable seamless session resumption across context boundaries.

Core Concept

A waypoint is NOT a memory. Memories are individual facts, decisions, or insights stored via mcp__vector-memory__store_memories. A waypoint is a session-level summary that ties memories together with project state, providing a resume point.

Waypoint = Session State Snapshot

  • Summary of work done
  • Key decisions and rationale
  • Items in progress or blocked
  • Concrete next steps
  • Links to related memory IDs

When to Set a Waypoint

After Completing a Discrete Task

Set a waypoint whenever a logical unit of work finishes:

  • Feature implementation complete
  • Bug fix verified
  • Refactoring done
  • Investigation concluded with findings

Anti-pattern: Setting a waypoint mid-task creates confusing resume points. Wait for a natural stopping point.

Before Clearing Context

Always set a waypoint before running /clear. Context clearing without a waypoint means losing all session state. The plugin's /clear detection hook provides a safety net, but explicitly setting one is better practice.

Before Switching Tasks

When pivoting to a different area of work, set the current state first. This preserves the mental model of the previous task for clean resumption later.

At Regular Intervals in Long Sessions

Long sessions accumulate context that becomes expensive to reconstruct. Set waypoints periodically to create recovery points. The plugin's context monitor warns at 50% and 75% context usage — treat these as waypoint prompts.

When to Load a Waypoint

Session Start

At the beginning of each session, load the waypoint to restore context. The plugin's SessionStart hook suggests this automatically. To continue previous work, accept; to start fresh, decline.

After Context Clearing

If context was cleared mid-project, load the waypoint to restore orientation.

Read the full file on GitHub · 155 lines

Changes

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.

  1. 9d ago First seen · 155 lines · 90 tokens per session scan A 950ca4d6f41a

Subscribe to this mod's changes

waypoint:workflow is a skill published in the GitHub repository aeriondyseti/vector-memory-mcp (5 stars, last pushed 2mo ago), licensed MIT. It adds 90 tokens to every session and 1,567 once invoked, about $0.0005 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-30.

Related

Other skills, from other repositories

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens