Agent skill · Audited from source
Memtrace Api Topology
skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 21 Oct 2026 · source 166077e7b684
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 166077e7b684 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Map API endpoints, outbound HTTP calls, and cross-repo service topology in indexed source code. Use when the user asks about API endpoints, HTTP routes, fetch/client calls, REST surface, service dependencies, cross-repo…
Cite
Cite this page
ModelsAtlas. “Memtrace Api Topology (syncable-dev/memtrace-public)”. Retrieved 21 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-api-topology
Trust audit
Audit 0.4.1 · source read 21 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 166077e7b684 · 21 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-api-topologyThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdict166077e7b684A 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: Map API endpoints, outbound HTTP calls, and cross-repo service topology in indexed source code. Use when the user asks about API endpoints, HTTP routes, fetch/client calls, REST surface, service dependencies, cross-repo…
---
name: memtrace-api-topology
description: "Map API endpoints, outbound HTTP calls, and cross-repo service topology in indexed source code. Use when the user asks about API endpoints, HTTP routes, fetch/client calls, REST surface, service dependencies, cross-repo dependencies, or API topology. Do not use Grep, Glob, rg, find, or manual file search for routes or HTTP calls; Memtrace maps endpoints and call edges from the indexed AST graph."
---
## Overview
Map HTTP API surface — endpoints, outbound calls, cross-repo topology.
## Quick Reference
| Tool | Required | Key optional |
|------|----------|--------------|
| `find_api_endpoints` | `repo_id` | `method`, `path_contains`, `limit`, `branch` |
| `find_api_calls` | `repo_id` | `method`, `path_contains`, `limit`, `branch` |
| `get_api_topology` | — | `repo_id`, `min_confidence`, `include_external` |
Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
## Steps
### 1–3. Endpoints, calls, topology
```json
{ "repo_id": "memdb" }
{ "repo_id": "memdb", "method": "GET", "path_contains": "/users" }
{ "min_confidence": 0.7 }
```
### 4. Deep-dive an endpoint handler
Use handler **symbol name** — not symbol ID:
```json
{ "repo_id": "memdb", "symbol": "handleGetUsers" }
```
## Output
| Result | Carries |
|--------|---------|
| Endpoint entry (`find_api_endpoints`) | HTTP method, route path, handler symbol name (feed to `get_symbol_context` as `symbol`) |
| Call entry (`find_api_calls`) | HTTP method, target path, calling symbol |
| Topology edge (`get_api_topology`) | caller repo → handler repo, confidence 0.0–1.0 (edges below `min_confidence` dropped) |
## Common Mistakes
| Mistake | Reality |
|---------|---------|
| `get_symbol_context(symbol_id=...)` | Use **`symbol`** (name) + `repo_id` |
| Cross-repo links with one repo indexed | Index all services; use `link_repositories` if needed |Excerpt, first 1,945 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 166077e
git clone https://github.com/syncable-dev/memtrace-public git -C memtrace-public checkout 166077e7b684
The author documents no install command, so this uses the repository directly. Our verdict covers commit 166077e7b684 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
166077e7b684
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 Api Topology
What does the Memtrace Api Topology skill do?
Is Memtrace Api Topology safe to install?
What can Memtrace Api Topology 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 166077e7b684 and every finding aboveObserved · 21 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 Api Topology skill do?
- Is Memtrace Api Topology safe to install?
- What can Memtrace Api Topology access on my machine?