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 aeriondyseti/vector-memory-mcp --skill waypoint-getgit clone --depth 1 https://github.com/aeriondyseti/vector-memory-mcpWrote 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/aeriondyseti/vector-memory-mcp/waypoint-get)<a href="https://agentmods.dev/skills/aeriondyseti/vector-memory-mcp/waypoint-get"><img src="https://agentmods.dev/badge/skills/aeriondyseti/vector-memory-mcp/waypoint-get/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/aeriondyseti/vector-memory-mcp/waypoint-get"><img src="https://agentmods.dev/badge/skills/aeriondyseti/vector-memory-mcp/waypoint-get.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.00014 | $0.00439 |
| Opus 5 | $0.00007 | $0.00219 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
waypoint:get 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 10d 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.
What it actually says
Load context for current project using vector-memory.
1. Check Git
git log --oneline -10 2>/dev/null
git branch --show-current 2>/dev/null
2. Fetch Waypoint
Call mcp__vector-memory__get_waypoint to retrieve the latest waypoint snapshot.
After reading waypoint, check for staleness:
git log --oneline --since="[waypoint date]" 2>/dev/null
If commits exist after waypoint: Show them, ask user whether to use waypoint or skip it.
If no waypoint exists: Note it and continue to step 3.
3. Search Memories
Call mcp__vector-memory__search_memories with:
- query: "[project name] architecture decisions patterns"
- intent: "continuity"
- reason_for_search: "Loading project context for session resumption"
- limit: 10
4. Load Referenced Memories
If the waypoint includes memory IDs, call mcp__vector-memory__get_memories with those IDs to retrieve full context.
5. Present Context
# Context: [Project]
**Dir:** [path] | **Branch:** [branch] | **Waypoint:** [date or None]
## Git Activity
[recent commits]
## State
[from waypoint summary, completed items, blockers]
## Next Steps
[from waypoint next_steps]
## Relevant Memories
[key memories from search + referenced memories]
6. Synthesize & Continue
Combine waypoint document with retrieved memories to establish full context. Then:
- Briefly acknowledge what was loaded (waypoint date + number of memories retrieved)
- Confirm current status and next steps from waypoint
- Ask: "Ready to continue with [next step], or is there a different direction?"
No waypoint / no memories: Just note it and ask what we're working on.
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.
- 10d ago First seen · 70 lines · 14 tokens per session scan A f78e01b3251a
waypoint:get is a skill published in the GitHub repository aeriondyseti/vector-memory-mcp (5 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 439 once invoked, about $0.0001 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.
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.
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.…
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…
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.
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…
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.