Agent skill · Audited from source
Memtrace Continuous Memory
skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 26 Oct 2026 · source 3e7894d935d8
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: Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing. Use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up…
Cite
Cite this page
ModelsAtlas. “Memtrace Continuous Memory (syncable-dev/memtrace-public)”. Retrieved 26 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-continuous-memory
Trust audit
Audit 0.4.1 · source read 26 Oct 2026
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
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
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 · 26 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-continuous-memoryThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdict3e7894d935d8A new audit runs when the source changes
- Repository statusNot archivedLast push 2 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing. Use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up…
---
name: memtrace-continuous-memory
description: "Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing. Use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up always-on memory (meaning Memtrace index watching, not generic agent memory), or make just-saved source code queryable immediately. Do not fall back to repeated Grep or manual rescans; configure Memtrace watching."
---
## Overview
Keep the knowledge graph live while editing. `watch_directory` triggers incremental re-indexing on file saves (~80 ms typical latency after debounce).
## Required parameters — `watch_directory`
| Param | Required | Notes |
|---|---|---|
| `path` | yes | Absolute directory path |
| `repo_id` | yes | Must already be indexed |
| `branch` | no | default `"main"` |
```json
{ "path": "/abs/path/to/repo", "repo_id": "memdb" }
```
Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
## Steps
### 1. Confirm indexed
```
list_indexed_repositories()
```
Run `index_directory` first if missing (poll `check_job_status`; stop after ~5 minutes and report the job id — see memtrace-index).
### 2. Start watching
See JSON above. Returns immediately; watcher runs in background.
### 3. Confirm active watches
```
list_watched_paths()
```
Response shape: see [Output](#output).
### 4. Edit normally
Next `find_symbol` / `get_symbol_context` call sees saved changes after debounce (~500 ms) + incremental persist (~80 ms).
### 5. Stop watching (kill switch)
`unwatch_directory`:
```json
{ "path": "/abs/path/to/repo" }
```
Idempotent — unwatching an already-unwatched path is a no-op.
## Latency expectations
| Stage | Typical |
|---|---|
| Debounce | **500 ms** (MCP schema) |
| Incremental persist | ~80 ms |
| Save → queryable | ~80–150 ms after debounce |
## Output
`watch_directory` returns an immediate acknowledgment; the watcher runs in the background. `list_watched_paths` returns:
```json
{
"watches": [
{ "path": "...", "repo_id": "...", "branch": "...", "started_at": "...", "origin": "..." }
],
"count": 1
}
```
There is **no `persist_ms`** field in this response.
## Common Mistakes
| Mistake | Reality |
|---------|---------|
| `watch_directory(path=...)` without `repo_id` | **Both required** |
| Watching unindexed repo | Index first |
| Expecting `persist_ms` from `list_watched_paths` | Field not in MCP response |
| Debounce "50 ms" | Schema documents **500 ms** |Excerpt, first 2,577 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
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
- ✓SAFE B 89 / 100
first audit · source
3e7894d935d8
Similar skills
All coding & review skills →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…
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,…
syncable-dev/memtrace-public
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…
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…
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,…
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,…
Questions about Memtrace Continuous Memory
What does the Memtrace Continuous Memory skill do?
Is Memtrace Continuous Memory safe to install?
What can Memtrace Continuous Memory access on my machine?
How current is this page?
Sources
- github.com/syncable-dev/memtrace-public/tree/main/plugins/memtra — the audited source at commit 3e7894d935d8 and every finding aboveObserved · 26 Oct 2026
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.
- What does the Memtrace Continuous Memory skill do?
- Is Memtrace Continuous Memory safe to install?
- What can Memtrace Continuous Memory access on my machine?