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

Agent skill · Audited from source

Memtrace Cochange

skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 22 Oct 2026 · source 51a5a6970061

★ 504pushed today
✓SAFEGrade B · 89/100 · 22 Oct 2026 · 51a5a69
504repo stars · whole syncable-dev/memtrace-public

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 51a5a6970061 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes. Use when the user asks about historical coupling, co-change, what changes with this, hidden dependencies,…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Memtrace Cochange (syncable-dev/memtrace-public)”. Retrieved 22 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-cochange

Trust audit

Audit 0.4.1 · source read 22 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 51a5a6970061 · 22 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-cochangeThe exact folder we audited
  • LicenceNOASSERTIONAs the repository states it
  • Commit pinned for this verdict51a5a6970061A 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: Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes. Use when the user asks about historical coupling, co-change, what changes with this, hidden dependencies,…

---
name: memtrace-cochange
description: "Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes. Use when the user asks about historical coupling, co-change, what changes with this, hidden dependencies, or what else needs to move for source code. Do not use git log, git diff, Grep, or manual file search to correlate changes; Memtrace queries co-change and temporal graph data directly."
---

## Overview

Find **files** that historically co-change with a target symbol or file path — ranked by co-occurrence frequency across git episodes. Surfaces **behavioral coupling** the static call graph cannot see.

`get_impact` answers "who calls this?" (structural).
`get_cochange_context` answers "what files always move when this moves?" (historical, file-level).

They are complementary. A file with no call-graph edges to the target can still be a strong cochange partner if it's always modified alongside it in every commit.

> **Parameter types:** Numbers (`limit`, `window_days`, etc.) must be JSON numbers — not strings.

## Required parameters

| Parameter | Required | Default | Notes |
|---|---|---|---|
| `repo_id` | yes | — | |
| `target` | yes | — | Symbol name **or** file path substring — **not** `symbol` |
| `limit` | no | **10** | Max cochanged files returned |
| `window_days` | no | **30** | Lookback from `as_of` |
| `as_of` | no | now | Window anchor |
| `branch` | no | any branch | |

```json
{
  "repo_id": "memdb",
  "target": "execute",
  "limit": 10,
  "window_days": 30
}
```

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

## Output

```json
{
  "cochanged_files": [
    {
      "file_path": "src/order/types.rs",
      "cochange_count": 8,
      "last_cochanged_at": "2026-04-13T10:43:00Z"
    }
  ],
  "target_files": ["src/order/service.rs"]
}
```

There is **no** `cochanges[]` with symbol names — results are **file-level**.

## Steps

### 1. Identify the target

Use `find_symbol` if needed. Pass the symbol **`name`** or a **`file_path`** as `target`.

### 2. Call `get_cochange_context`

See required parameters above.

### 3. Interpret results

High `cochange_count` on a file → strong historical coupling. When you modify the target, review those files too — even without direct call-graph edges.

### 4. Cross-reference with call graph

For symbols in cochanged files, optionally run `get_impact(target=...)`:

| Structural coupling | Historical coupling | Interpretation |
|---|---|---|
| Yes | Yes | Core dependency — highest risk |
| No | Yes | Hidden coupling — history-only |
| Yes | No | Called often but changed independently |

## Use Cases

- **Before modifying a symbol** — get blast awareness beyond what `get_impact` shows
- **Incident investigation** — when `get_impact` doesn't explain the blast radius, check cochange history
- **Code review** — verify that a PR touched all historically-coupled partners
- **Refactoring** — discover implicit coupling before extracting a module

## Common Mistakes

| Mistake | Reality |
|---------|---------|
| Only using `get_impact` for blast radius | Structural coupling misses behavioral coupling — always pair with cochange |
| Ignoring cochanged files with no call-graph edges | A rarely-called file with high `cochange_count` is a strong coupling signal |
| Using cochange as a dependency map | It's a change correlation, not a dependency graph — files can cochange without any direct relationship |
| Passing `symbol:` | Required param is **`target`** |
| Expecting `cochanges[]` with symbol names | Response is **`cochanged_files[]`** (file paths) |
| Using `limit: 20` as default | API default is **10** |
| Empty results with 0 git episodes | Run `replay_history` during indexing to populate co-change data |

Excerpt, first 3,841 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 51a5a69

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

The author documents no install command, so this uses the repository directly. Our verdict covers commit 51a5a6970061 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 51a5a6970061

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 Cochange

What does the Memtrace Cochange 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 Cochange 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 Cochange 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 (51a5a6970061), read on 2026-10-22. 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.