Borrowing it
Nothing to install: this file belongs to larsbaunwall/Unlinked. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/larsbaunwall/Unlinked/main/.agents/skills/linkedin-member-data-portability/SKILL.mdgit clone --depth 1 https://github.com/larsbaunwall/UnlinkedWrote 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/larsbaunwall/unlinked/linkedin-member-data-portability)<a href="https://agentmods.dev/skills/larsbaunwall/unlinked/linkedin-member-data-portability"><img src="https://agentmods.dev/badge/skills/larsbaunwall/unlinked/linkedin-member-data-portability/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/larsbaunwall/unlinked/linkedin-member-data-portability"><img src="https://agentmods.dev/badge/skills/larsbaunwall/unlinked/linkedin-member-data-portability.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.00053 | $0.01507 |
| Opus 5 | $0.00026 | $0.00754 |
| Sonnet 5 | $0.00011 | $0.00301 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
linkedin-member-data-portability 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Member Data Portability API
Use this skill whenever you implement or review LinkedIn API behavior for Unlinked.
Product Context
Unlinked uses LinkedIn's Member Data Portability (Member) API product. The purpose is to let a LinkedIn member connect their own professional profile and experience data to an AI assistant through a local MCP server. The API is read-only for this project.
This API product exists for DMA data portability and is currently available only to LinkedIn members located in the European Economic Area and Switzerland. User-facing setup and error messages should say this plainly.
Access And Tokens
- A LinkedIn Developer application must be provisioned with Member Data Portability API (Member).
- LinkedIn's OAuth Token Generator docs currently instruct users to request
r_dma_portability_self_servefor member self-serve access. - Snapshot and changelog docs also reference
r_dma_portability_memberandr_dma_portability_3rd_partypermissions. Treat 403 responses as likely product/scope/consent problems and explain that clearly. - MCP clients should provide the access token as secret tool input for stdio usage. The server should send it only as
Authorization: Bearer <access_token>to LinkedIn. - Never store, log, return, or include access tokens in thrown errors.
Required Headers
Every LinkedIn REST call should include:
Authorization: Bearer <access_token>
Linkedin-Version: <YYYYMM>
Content-Type: application/json
Use the exact header name Linkedin-Version. Make the version configurable where useful. The changelog docs mention 202312, while the current documentation version is 2025-11; verify the latest supported version before changing defaults.
Snapshot API
Use the Snapshot API for profile and professional-history data.
GET https://api.linkedin.com/rest/memberSnapshotData?q=criteria
GET https://api.linkedin.com/rest/memberSnapshotData?q=criteria&domain=PROFILE
The optional domain query parameter is case-sensitive. If omitted, LinkedIn may return all domains. Prefer explicit domains for predictable assistant-facing tools.
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 · 143 lines · 53 tokens per session scan A 4c2a384e30b0
linkedin-member-data-portability is a skill published in the GitHub repository larsbaunwall/Unlinked (3 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,507 once invoked, about $0.0003 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-31.
Other skills, from other repositories
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
mcp-google-map-project
Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…