Agent skill · Audited from source
Memtrace Impact
skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 28 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: Compute the blast radius of modifying a symbol through transitive graph impact. Use when the user asks about blast radius, impact, what breaks, risk, upstream callers, downstream dependencies, or consequences of…
Cite
Cite this page
ModelsAtlas. “Memtrace Impact (syncable-dev/memtrace-public)”. Retrieved 28 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-impact
Trust audit
Audit 0.4.1 · source read 28 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 · 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-impactThe 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: Compute the blast radius of modifying a symbol through transitive graph impact. Use when the user asks about blast radius, impact, what breaks, risk, upstream callers, downstream dependencies, or consequences of…
---
name: memtrace-impact
description: "Compute the blast radius of modifying a symbol through transitive graph impact. Use when the user asks about blast radius, impact, what breaks, risk, upstream callers, downstream dependencies, or consequences of modifying a symbol, before or during source-code changes. Do not use Grep or manual reference search; Memtrace computes transitive graph impact. For a full risk-rated plan covering a multi-part change, use memtrace-change-impact-analysis."
---
## Overview
Compute the blast radius of changing a specific symbol. Traces upstream (what depends on this) and downstream (what this depends on) through the knowledge graph to quantify risk before making modifications.
## Quick Reference
| Tool | Purpose |
|------|---------|
| `get_impact` | Blast radius from a symbol **name** (`target`) |
| `detect_changes` | Scope symbols affected by a diff/patch |
> **Parameter types:** MCP parameters are strictly typed. Numbers (`depth`, `limit`, etc.) must be JSON numbers — not strings.
## Required parameters — `get_impact`
| Parameter | Required | Default | Notes |
|---|---|---|---|
| `repo_id` | yes | — | |
| `target` | yes | — | Symbol name (e.g. `"validateToken"`) — **not** `symbol_id` |
| `direction` | no | `"both"` | `"upstream"` \| `"downstream"` \| `"both"` |
| `depth` | no | `5` | BFS depth (max 15) |
| `as_of` | no | now | ISO-8601 for time-travel |
```json
{ "repo_id": "memdb", "target": "validateToken", "direction": "both", "depth": 5 }
```
Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
## Steps
### 1. Identify the symbol name
If you don't know the exact name:
- `find_symbol(name="...")` for exact identifiers
- `find_code(query="...")` for natural-language queries
Use the returned **`name`** (and optional `file_path` hint) — graph tools resolve by name, not internal IDs.
### 2. Run impact analysis
```json
{
"repo_id": "memdb",
"target": "validateToken",
"direction": "upstream",
"depth": 5
}
```
### 3. Interpret the risk rating
| Risk | Meaning | Action |
|------|---------|--------|
| **Low** | Few dependents, leaf node | Safe to modify; minimal testing needed |
| **Medium** | Moderate dependents | Test direct callers; review interface contracts |
| **High** | Many dependents across modules | Coordinate changes; comprehensive test coverage |
| **Critical** | Core infrastructure, many transitive dependents | Plan migration strategy; backward-compatible changes |
### 4. For diff-based analysis
When you have an actual code diff, use `detect_changes`:
```json
{ "repo_id": "memdb", "diff": "<unified git diff text>" }
```
Or pass `changed_files: ["path/a.rs", "path/b.ts"]` when no diff text is available.
## Decision Points
| Situation | Action |
|-----------|--------|
| Changing a single function | `get_impact` with `direction: "both"` |
| Reviewing a PR or diff | `detect_changes` with the diff content |
| Renaming/removing a public API | `get_impact` with `direction: "upstream"`, higher `depth` |
| Refactoring internals | `get_impact` with `direction: "downstream"` |
## Output
`get_impact` returns the blast radius for the target symbol:
| Field | Example / meaning |
|---|---|
| Risk rating | `High` — one of `Low` / `Medium` / `High` / `Critical` (interpret via step 3) |
| Upstream | Transitive dependents (callers/importers) within `depth` hops — what breaks if the target changes |
| Downstream | Transitive dependencies — what the target relies on |
`detect_changes` returns the set of symbols affected by the supplied `diff` / `changed_files`, plus the affected processes (execution flows).
## Common Mistakes
| Mistake | Reality |
|---------|---------|
| Passing `symbol_id` or `name` | Required param is **`target`** |
| Omitting `repo_id` | Both `repo_id` and `target` are required |
| Defaulting `depth` to 3 | API default is **5** |Excerpt, first 3,942 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 Impact
What does the Memtrace Impact skill do?
Is Memtrace Impact safe to install?
What can Memtrace Impact 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 · 28 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 Impact skill do?
- Is Memtrace Impact safe to install?
- What can Memtrace Impact access on my machine?