link-memory — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited link-memory (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use explicit memory operations. In a source checkout, replace lnk with python3 link.py. Do not silently save durable memory; only remember when the user asks or approves a proposal.
lnk brief "<current task>" [link-root] lnk recall "<topic>" [link-root] lnk remember "<user-approved memory>" [link-root] --type note --scope userUse --project <slug> for project-scoped memory, --visibility private|project|team for sharing intent, --review-after YYYY-MM-DD for stale-risk memories, and --expires-at YYYY-MM-DD for temporary context.
lnk memory-inbox [link-root]
lnk explain-memory <name-or-title> [link-root]
lnk review-memory <name-or-title> [link-root] lnk update-memory <name-or-title> "<new text>" [link-root]
lnk archive-memory <name-or-title> [link-root] --reason "<why>"
lnk restore-memory <name-or-title> [link-root]
lnk forget-memory <name-or-title> [link-root] --confirmWhen duplicate or conflict warnings appear, prefer updating, reviewing, or archiving existing memory over creating another page.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.