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

Agent skill · Audited from source

Memtrace First

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

★ 505pushed today
✓SAFEGrade B · 89/100 · 28 Oct 2026 · 3e7894d
505repo 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: Route code discovery, debugging, flow tracing, how-code-works questions, and pre-edit rationale checks in indexed source-code repos to Memtrace graph plus Cortex decision tools. Use first before searching/reading code,…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Memtrace First (syncable-dev/memtrace-public)”. Retrieved 28 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-first

Trust audit

Audit 0.4.1 · source read 28 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 · 28 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-firstThe 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: Route code discovery, debugging, flow tracing, how-code-works questions, and pre-edit rationale checks in indexed source-code repos to Memtrace graph plus Cortex decision tools. Use first before searching/reading code,…

---
name: memtrace-first
description: "Route code discovery, debugging, flow tracing, how-code-works questions, and pre-edit rationale checks in indexed source-code repos to Memtrace graph plus Cortex decision tools. Use first before searching/reading code, and before editing, refactoring, deleting, or re-picking an approach that may have a recorded decision, ban, convention, or contract. Do not use Grep, Glob, rg, find, or manual file browsing for code discovery when Memtrace is indexed. Zero results are not permission to grep; diagnose/reindex with Memtrace."
---

# Memtrace First

## The Iron Law

```
IF THE REPO IS INDEXED IN MEMTRACE → USE MEMTRACE TOOLS FIRST.
After a search hit, route to GRAPH tools (get_symbol_context, get_impact,
analyze_relationships) — that's what Memtrace uniquely provides. Read source
ONLY when you're about to edit or quote, and read only the bounded span
returned by Memtrace (start_line .. end_line + small context). Do not
Grep/Glob/Find to "locate" anything already in the graph, and do not read
the whole file when Memtrace has given you exact lines.

BEFORE you edit/refactor/delete existing code or choose/re-pick a pattern,
call Cortex decision memory: recall_decision for the symbol/subsystem/approach,
and use provenance/contracts when a symbol_id is available. Use Memtrace's graph
tools for structure and blast radius; use Cortex for rationale, bans, and
contracts.
```

Memtrace is the **memory layer** of the codebase, not a search engine that returns code. It has the full knowledge graph — every symbol, call, import, community, process, and API — with a time dimension. The point is to navigate that graph: who calls this, what's the blast radius, when did this change, what community is it part of. File tools are blind to all of that.

**No exceptions for what's in the graph.**

## Value Tracking

Do not print usage receipts in normal answers. Memtrace records tool usage, graph facts, file references, and estimated context avoided internally. Users can inspect that in the local UI's Value panel.

## What Memtrace actually indexes

Memtrace's hybrid search = **BM25 over symbol metadata** (name, signature, file_path, kind) **+ semantic vector search over embedded code bodies** (first ~1500 chars of every Function / Method / Class / Struct / Interface body), fused via Reciprocal Rank Fusion.

The semantic side means **string literals, error messages, magic constants, log strings, and any text inside an indexed symbol's body are findable through `find_code`**. The body got embedded; the embedding catches it. You do NOT need `Grep` to hunt for `STRIPE_KEY_FOO_BAR` if it lives inside a function in your indexed codebase.

## Zero results are not a grep license

If Memtrace returns 0 results, or repository stats look incomplete, do **not**
infer that a source subdirectory is outside the index. Diagnose through
Memtrace:

1. Call `list_indexed_repositories` and identify the repo root/repo_id.
2. If the path is under that indexed repo root, keep using Memtrace.
3. Retry with broader `find_code` terms and, when available, `file_path` filters
   such as `ui/`, `memtrace-ui/`, `src/`, or the framework directory.
4. If the language/path still appears missing, run `index_directory` on the repo
   root with `incremental: true` (or ask before `clear_existing: true`).
5. Report the indexing coverage problem instead of silently switching to grep.

### Workspace Boundary Check

Before indexing or reindexing, make sure the target path is the repo the user
asked about. If the current folder is only a parent that contains multiple
independent git repos, do **not** index the parent just because it is the open
editor folder. That creates or reuses a shared `.memdb` and can make agents
answer from stale repos.

- For separate repos: use the actual git repo root as the `index_directory`
  path, or ask the user to open/run the agent from that repo root.
- For an intentional shared workspace: the user should bless it explicitly with
  `memtrace start --bless-workspace`, then verify it with
  `memtrace workspace status <path>`; the workspace marker should be present.
- If `list_indexed_repositories` returns empty or its metadata says the MCP
  child resolved a data dir from cwd because no workspace marker/git root was
  found, surface the workspace mismatch. Do not "fix" it by indexing the broad
  parent folder.

**Never say "the index only covers X, so grep is right" when the target path is
inside the indexed repository.** That is an indexing freshness/coverage issue,
not permission to abandon Memtrace.

## The narrow exceptions where grep/glob are still right

These are the ONLY cases where file tools beat memtrace:

- **Files outside every indexed repo root.** Confirm this with
  `list_indexed_repositories`; 0 search results or missing language stats do not
  prove it. Vendored deps, system headers, and excluded dirs
  (`.git`, `node_modules`, `target`, `dist`) are examples Memtrace cannot see.
- **Non-source artifacts.** `.env`, `package.json`, build scripts, top-level `README.md`, raw config files. Memtrace indexes parseable code, not configuration text.
- **Pure file-inventory questions.** "How many `*.test.ts` files exist", "list every Markdown file in `docs/`". You're asking for a file count, not a symbol search.
- **Reading at a known path outside Memtrace.** For configs, docs, or non-source artifacts that Memtrace cannot index, file `Read` is fine. For source-code spans returned by Memtrace, read the precise line range (your harness's `Read` with offset/limit, or `get_source_window` if your harness lacks bounded reads). Do not whole-file Read when you have a span.

For everything else inside the indexed repo, memtrace is the right tool.

## The decision rule

| Question Claude is asking | Right tool |
|---|---|
| "Where is symbol `foo` defined?" | `find_symbol(name="foo")` → then `get_symbol_context` for callers/callees/community, NOT a source read unless you're editing. |
| "

Excerpt, first 6,000 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

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 Session Continuity✓SAFE

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…

★ 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

Questions about Memtrace First

What does the Memtrace First 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 First 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 First access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (3e7894d935d8), read on 2026-10-28. 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.