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-healthgit 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-health)<a href="https://agentmods.dev/skills/gowtham0992/link/link-health"><img src="https://agentmods.dev/badge/skills/gowtham0992/link/link-health/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-health"><img src="https://agentmods.dev/badge/skills/gowtham0992/link/link-health.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.00041 | $0.00378 |
| Opus 5 | $0.00020 | $0.00189 |
| Sonnet 5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
link-health 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 9d 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 Health
Use the lnk CLI. Load this skill before trusting a new or changed Link wiki, after installs/upgrades, and before broad repair or restore work. In a source checkout, replace lnk with python3 link.py. MCP and the local web viewer are optional; lnk serve is only for humans to browse the wiki.
- Check readiness first:
lnk health [link-root] - If the output mentions interrupted or stale operations, inspect them before repair:
lnk operations [link-root] - Before broad repairs, migrations, or restore work, create a backup:
lnk backup [link-root] - Repair only generated or structural state that Link reports as safe:
lnk doctor --fix [link-root] lnk rebuild-index [link-root] lnk rebuild-backlinks [link-root] - Validate before saying the wiki is healthy:
lnk validate [link-root] lnk health [link-root]
If the user asks whether MCP is ready, run lnk verify-mcp [link-root]. Do not start lnk serve for MCP or CLI work.
To check whether optional local semantic recall is active (lexical is always the fallback):
lnk semantic [link-root]
It reports the provider tier, model, and index state, and prints the exact setup command when the layer is available but not yet enabled.
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.
- 9d ago First seen · 41 lines · 41 tokens per session scan A 030cb4d7f6ba
link-health is a skill published in the GitHub repository gowtham0992/link (179 stars, last pushed 7d ago), licensed MIT. It adds 41 tokens to every session and 378 once invoked, about $0.0002 per session on Opus 5. 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-ingest
Process raw source documents into wiki pages. Use when the user adds files to raw/ and wants them ingested, says "process this source", "ingest this article", "I added something to raw/", or wants to incorporate new material into their knowledge base.
second-brain-lint
Health-check the wiki for contradictions, orphan pages, stale claims, and missing cross-references. Use when the user says "audit", "health check", "lint", "find problems", or wants to improve wiki quality.
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.
code-understand
Build a ranked, citation-backed focus map of a codebase — the files and symbols an architecture actually hangs on — using CodeGraph when available and a dependency-free builtin (regex AST extraction + rg cross-file references) otherwise. Use this any time you (the coding agent) need to orient in an unfamiliar or large…
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.