Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add gowtham0992/link --skill link-memorygit clone --depth 1 https://github.com/gowtham0992/linkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gowtham0992/link/link-memory)<a href="https://agentmods.dev/skills/gowtham0992/link/link-memory"><img src="https://agentmods.dev/badge/skills/gowtham0992/link/link-memory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gowtham0992/link/link-memory"><img src="https://agentmods.dev/badge/skills/gowtham0992/link/link-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00601 |
| Opus 5.5 | $0.00000 | $0.00240 |
| Sonnet 5.5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
link-memory scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Link Memory
Use this skill after important user-approved decisions, preference changes, project conventions, or long work sessions that may deserve durable context. In a source checkout, replace lnk with python3 link.py. Do not silently save durable memory; propose first unless the user directly asks to remember, approves a proposal, or explicitly confirms an important decision should become durable memory.
If Link session hooks are installed for this agent, the memory brief is injected automatically at session start — skip step 1 and go straight to task-specific recall.
-
Prime before work:
lnk brief "<current task>" [link-root] -
Recall specific memory:
lnk recall "<topic>" [link-root] -
End a session with proposal-only memory candidates:
lnk session-end <session-notes-or-transcript> [link-root] --limit 3Use
-as the input when piping a transcript on stdin. Show the proposals to the user; do not save durable memory until the user approves one. -
Save an explicit memory:
lnk remember "<user-approved memory>" [link-root] --type note --scope userUse
--project <slug>for project-scoped memory,--visibility private|project|teamfor sharing intent,--review-after YYYY-MM-DDfor stale-risk memories, and--expires-at YYYY-MM-DDfor temporary context. When a brief or recall reports a memory backlog (pending captures or reviews above threshold), offer the user a short consolidation pass:lnk consolidate [link-root]The plan is read-only: it groups duplicates and recurring themes and prints accept/discard/review commands. Apply an action only after the user approves it.
-
Review and explain before trusting uncertain memory:
lnk memory-inbox [link-root] lnk explain-memory <name-or-title> [link-root] lnk review-memory <name-or-title> [link-root] -
Change lifecycle safely:
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] --confirm
When duplicate or conflict warnings appear, prefer updating, reviewing, or archiving existing memory over creating another page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 51 lines · 0 tokens per session scan A 3aa8ee93bd60
link-memory is a skill published in the GitHub repository gowtham0992/link (216 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 601 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
second-brain
Set up a new Obsidian knowledge base with the LLM Wiki pattern. Use when the user wants to create a second brain, initialize a vault, set up a personal knowledge base, or says "onboard". Guides through an interactive wizard to configure vault name, location, domain, agent support, and tooling.
second-brain-query
Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki.
llmwiki
Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
kb-init
Use when setting up a new knowledge base, bootstrapping an Obsidian vault, or when user says 'init kb', 'new knowledge base', 'create kb', or 'setup vault'. Triggers on any request to initialize or scaffold a knowledge base project.
obsidian-setup-consultant
Use this skill whenever the user wants to install, configure, migrate, design, or connect Obsidian as a second brain, knowledge base, cloud-synced vault, or AI/Hermes-readable memory. It is especially important when the user asks for an Obsidian setup prompt, vault architecture, folder structure, plugin…