Is repo-graph-orient safe to install?

SaferSkills independently audited repo-graph-orient (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/repo-graph-orient/SKILL.md · 1 file

skills/repo-graph-orient/SKILL.md1.1 KB · Markdown

name: repo-graph-orient

description: Get oriented in a codebase before reading files — repo shape, the full structural map, and a visual tree. Use at the start of any task in an unfamiliar or large repo.

repo-graph orient

Build a mental model of the repo from the graph instead of opening files one by one.

When to use

Starting work in an unfamiliar or large repo.
The user asks "how does this codebase work?" or "what's in here?".
Before any change, to learn the lay of the land cheaply.

Steps

Call status first — node/edge counts, detected kinds, entry points, and a dense-text preview. This is the orient call; do it before grepping.
For the whole picture, call dense_text — the full graph in dense notation. Read it instead of reading files; it's the primary context source. Large graphs are truncated, so scope with find/activate/flow if needed.
For a visual, call graph_view — no argument for an overview, or a node name for a tree around it.

Report the tiers (entry → service → handler → data) and the main entry points. You now know where to look without having opened a file.

repo-graph-orient— agent skill

Is repo-graph-orient safe to install?

repo-graph orient

When to use

Steps

Audit the pieces. Scan the whole. Decide.