Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/lanes-sh/link/lanes-link)<a href="https://agentmods.dev/skills/lanes-sh/link/lanes-link"><img src="https://agentmods.dev/badge/skills/lanes-sh/link/lanes-link/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/lanes-sh/link/lanes-link"><img src="https://agentmods.dev/badge/skills/lanes-sh/link/lanes-link.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00134 | $0.07360 |
| Opus 5 | $0.00067 | $0.03680 |
| Sonnet 5 | $0.00027 | $0.01472 |
| Haiku 4.5 | $0.00013 | $0.00736 |
Grade A, and why
lanes-link 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 579 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lanes Link
A self-hostable gateway to one person's own context: the accounts they have connected, the knowledge they have accumulated, the procedures they have written down, and their secrets. One endpoint serves every profile in a workspace, and each call names which profile it means.
The endpoint describes its own live state when you connect — which profiles
exist, what is reachable in each — and serves the long form of this at
lanes://instructions. This file is the part that does not change: how to
behave with it.
Three words, and they changed in 0.8.0
A connection is one authorised account, and it belongs to the workspace. A profile is a selection: which connections it includes, what it allows on each, and who may consume it.
That ordering is the change. A connection used to live inside one profile, so reaching the same mailbox from two of them meant authorising it twice, and every account of a provider within a profile was governed identically. Now the account is authorised once and each profile decides what it may do with it, which is what makes "read this mailbox, write that calendar" something a person can write down.
"Target" is gone. It named the thing a workspace already was. --workspace
is the flag; --target still works for one minor and warns.
Profiles are a boundary, not a setting
Every tool takes profile and connection. Profiles are how someone keeps work
and personal apart; a connection they do not grant is not visible in one at all.
Ask which profile is meant when it is ambiguous. Do not default to whichever
is listed first. Quietly picking one crosses the line the profile exists to
draw. There is no "current profile" to switch — the choice is made per call, and
lanes link profile list --workspace <name> shows what exists in that
workspace. A profile lives in exactly one, so personal on local and
personal on cloud are two profiles that share a name rather than one profile
in two places.
A profile owns its data. Two profiles granting the same connection — every
profile grants lanes_memory.lan1 — still read and write different notes,
tasks, files and entities, because the profile is part of where they are kept.
So there is nothing to be found in one by asking another, and a note taken under
work is not available under personal.
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.
- yesterday Changed · +3 lines a49e3ad98cb8
- 5d ago Changed · +113 lines · +13 tokens per session f491725a3538
- 9d ago First seen · 463 lines · 121 tokens per session scan A bc4912091155
lanes-link is a skill published in the GitHub repository lanes-sh/link (34 stars, last pushed today), licensed Apache-2.0. It adds 134 tokens to every session and 7,360 once invoked, about $0.0007 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
memories-off
A local knowledge-base skill that stores people, projects, notes, and their relationships in Markdown files. It supports long-term memory for an AI assistant.
obsidian-web-mcp
Set up or maintain an Obsidian vault with a desktop ChatGPT web sidebar community plugin and a vault-scoped MCP server exposed through ngrok. Use when asked to configure Obsidian plugins, install or update a ChatGPT web sidebar, expose an Obsidian vault to ChatGPT/MCP, add read/write vault tools, add Agent…
gptadmin-workflow
Run profile-first GPTAdmin workflows that route memory and MCP work to the services named by the active configuration.
reef
Read and maintain a person's private and shared long-term Reef memory through the reef CLI. Use when an agent needs remembered context, pages, coves/coves, files, invitations, persona settings, or carefully confirmed sharing in Reef; also use when the user asks to remember something for later.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.