Live survey304 models · 14 providers · 23,592 auditsAudited implement · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Memtrace Session Continuity

skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 31 Oct 2026 · source 3e7894d935d8

★ 509pushed today
✓SAFEGrade B · 89/100 · 31 Oct 2026 · 3e7894d
509repo stars · whole syncable-dev/memtrace-public

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 3e7894d935d8 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Catch up on everything that changed in an indexed source-code repo since the last session, using stored session anchors and Memtrace change memory. Use when the user asks to continue, catch up, resume, see what changed…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Memtrace Session Continuity (syncable-dev/memtrace-public)”. Retrieved 31 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-session-continuity

Trust audit

Audit 0.4.1 · source read 31 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 3e7894d935d8 · 31 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publishersyncable-dev GitHub organizationOwner of the repository this skill is read from
  • Source foldersyncable-dev/memtrace-public/plugins/memtrace-skills/skills/memtrace-session-continuityThe exact folder we audited
  • LicenceNOASSERTIONAs the repository states it
  • Commit pinned for this verdict3e7894d935d8A new audit runs when the source changes
  • Repository statusNot archivedPushed today
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Catch up on everything that changed in an indexed source-code repo since the last session, using stored session anchors and Memtrace change memory. Use when the user asks to continue, catch up, resume, see what changed…

---
name: memtrace-session-continuity
description: "Catch up on everything that changed in an indexed source-code repo since the last session, using stored session anchors and Memtrace change memory. Use when the user asks to continue, catch up, resume, see what changed while away, recover prior context, or orient at session start without guessing timestamps. Do not use git log, Grep, or manual file search for catch-up; Memtrace provides session anchors and change memory."
---

## Overview

Session continuity for agents. Store a timestamp from your last session and call `get_changes_since` to see exactly what happened since then — then drill into details with `get_evolution` if needed.

**Core principle:** Persist a `since` timestamp (or the `until` from your last catch-up call). Never invent a `days` parameter.

## Steps

### 1. Find or bootstrap the session anchor

Look for a stored anchor from your last session:

```json
{
  "repo_id": "memdb",
  "since": "2026-04-13T10:43:00Z"
}
```

If you have no anchor yet (first run), call `list_indexed_repositories`. Use `last_episode_time` from the repo entry as a bootstrap `since` value, or ask the user how far back to look.

### 2. Call `get_changes_since`

```json
{
  "repo_id": "memdb",
  "since": "2026-04-13T10:43:00Z"
}
```

Optional: pass `until` to cap the upper bound (defaults to now).

**Required param is `since`** — not `last_episode_id`, not `days`. Same time formats as `get_evolution.from` (`"7d ago"`, ISO-8601, etc.).

Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).

### 3. Interpret the response

Response shape: see [Output](#output) below. Act on `totals.episode_count`:

| `totals.episode_count` | Action |
|---|---|
| `0` | Nothing changed — safe to proceed |
| `1–20` | Review each episode's `touched_files` and change counts |
| Many episodes | Scan `touched_files` for overlap with your task; drill down with `get_evolution` |

### 4. Decide whether changes are relevant

```
episodes returned
├── Any touched_files overlap your current task area?
│   ├── YES → call get_evolution(from: since, mode: compound) for hotspots
│   └── NO  → safe to continue
└── Need per-commit detail?
    └── get_evolution(from: since, mode: recent, limit: 100)
```

### 5. Always persist the new anchor

Store the `until` value from the response (or the latest episode's `reference_time`) for next session:

```json
{
  "repo_id": "memdb",
  "since": "2026-04-13T14:22:00Z"
}
```

## Output

`get_changes_since` returns:

| Field | Meaning |
|---|---|
| `episodes[]` | Each episode since `since`, with `touched_files`, `nodes_added/removed`, `reference_time` |
| `totals.episode_count` | How many episodes in the window — `0` means nothing changed |
| `since` / `until` | The resolved window boundaries |

```json
{
  "since": "2026-04-13T10:43:00Z",
  "until": "2026-04-13T14:22:00Z",
  "episodes": [
    { "reference_time": "2026-04-13T12:05:00Z", "touched_files": ["src/engine/page_cache.rs"], "nodes_added": 4, "nodes_removed": 1 }
  ],
  "totals": { "episode_count": 1 }
}
```

## Common mistakes

| Mistake | Reality |
|---|---|
| Passing `last_episode_id` or `days` | `get_changes_since` requires `since` — a timestamp string |
| Using `get_evolution` without `from` | Always pass `from` (e.g. `"7d ago"`) — never omit it or use `days` |
| Expecting `status`, `by_module`, or `session_anchor` in the response | Not in the current shape — use `episodes[]` and `totals` |
| Discarding the stored `since` timestamp | Without it, next session reverts to guessing |
| Calling this repeatedly within one session | Call once at session start; reuse the result for the rest of the session |

Excerpt, first 3,736 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 3e7894d

Download folder ↗
git clone https://github.com/syncable-dev/memtrace-public
git -C memtrace-public checkout 3e7894d935d8

The author documents no install command, so this uses the repository directly. Our verdict covers commit 3e7894d935d8 only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 3e7894d935d8

README badge

For maintainers · shows the latest audit

ModelsAtlas: SAFE BMODELSATLASSAFE · B
[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/syncable-dev/memtrace-session-continuity/badge.svg)](https://modelsatlas.com/skills/syncable-dev/memtrace-session-continuity/)

The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.

Memtrace Relationships✓SAFE

syncable-dev/memtrace-public

Map source-code relationships between symbols. Use when the user asks about callers, callees, references, imports, exports, type usages, class hierarchy, inheritance, implementations, overrides, or dependencies between…

★ 509Grade B
Memtrace Search✓SAFE

syncable-dev/memtrace-public

Find source code with Memtrace hybrid BM25+semantic search: symbols, functions, classes, types, constants, definitions, implementations, logic, or error strings inside code. Use when the user wants to find, search,…

★ 509Grade B
Memtrace Index✓SAFE

syncable-dev/memtrace-public

Index a source-code repo into the Memtrace knowledge graph and poll the job to completion. Use when the user asks to index, parse, ingest, reindex, watch, or prepare a source-code repo for Memtrace analysis, when code…

★ 508Grade B
Memtrace Quality✓SAFE

syncable-dev/memtrace-public

Find dead code, complexity hotspots, and refactoring candidates in indexed source code. Use when the user asks about source-code quality, dead code, unused functions, zero callers, complexity, cyclomatic complexity,…

★ 508Grade B
Memtrace Refactoring Guide✓SAFE

syncable-dev/memtrace-public

Build a phased, risk-scored refactoring plan from Memtrace complexity, dead-code, bridge, impact analysis, and Cortex decision-memory constraints. Use when the user wants to refactor source code, reduce complexity,…

★ 508Grade B
Memtrace Code Review✓SAFE

syncable-dev/memtrace-public

Review GitHub pull requests with Memtrace's local graph-backed review engine. Use when the user asks to review a GitHub pull request, run Memtrace code review, post Memtrace review comments, create a PR with a review…

★ 506Grade B

Add this badge to your README

[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/syncable-dev/memtrace-session-continuity/badge.svg)](https://modelsatlas.com/skills/syncable-dev/memtrace-session-continuity/)

Questions about Memtrace Session Continuity

What does the Memtrace Session Continuity skill do?
Structural memory for AI coding agents. Bi-temporal graph, MCP-native, zero LLM calls. Cursor · Claude Code · Codex · DeepSeek Harness · Hermes · VS Code · Windsurf.
Is Memtrace Session Continuity safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Memtrace Session Continuity access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
What do I need installed to use Memtrace Session Continuity?
Its own instructions reference since. Dependencies are pinned to exact versions.
How current is this page?
The grade is for one exact copy of the source (3e7894d935d8), read on 2026-10-31. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.