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 agentmods add skills/context-dot-dev/cursor-plugin/logolinknpx skills add context-dot-dev/cursor-plugin --skill logolinkgit clone --depth 1 https://github.com/context-dot-dev/cursor-pluginWhat 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 | $0.00057 | $0.00933 |
| Opus 5 | $0.00028 | $0.00466 |
| Sonnet 5 | $0.00011 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
logolink 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context.dev Logo Link
Logo Link delivers company logos via CDN. Pass a front-end-safe publicClientId and a domain; the URL returns raw image bytes (no JSON, no API key).
Do not use the brand API or MCP from browser/client code for logos. Use Logo Link instead.
When to use
- User wants logos in a UI, landing page, CRM, directory, or transaction list
- User asks to "dynamically fetch/display company logos by domain"
- High-volume logo rendering where
ctxt_secret_keys must stay server-side - User needs a simple
<img src="...">instead of parsingbrand.logos[]
Use the brand API (see context-dev skill) when you need stored logos, multiple variants (light/dark/icon), or colors alongside the image.
Step 1 — Get the Public Client ID
- Sign up at context.dev/signup if needed (free tier: 10,000 Logo Link requests/month).
- Copy the Public Client ID from context.dev/dashboard/logolink. Keys look like
brandLL_xxx. - Prefer an env var the codebase already uses, e.g.
NEXT_PUBLIC_LOGOLINK_KEYorVITE_LOGOLINK_PUBLIC_CLIENT_ID. Never put a private Context.dev API key in client code.
Step 2 — Restrict referring domains
In the Logo Link dashboard, Edit Restrictions and allow only domains that embed the image (e.g. *.example.com, localhost:3000). The publicClientId is safe in frontend code only when restrictions are set.
Step 3 — Build the URL
https://logos.context.dev/?publicClientId=MY_PUBLIC_CLIENT_ID&domain=TARGET_DOMAIN
- Replace
MY_PUBLIC_CLIENT_IDwith the user's ID (or env var). - Replace
TARGET_DOMAINwith the company domain variable (bare domain, e.g.stripe.com). - Optionally add
theme=lightfor a dark logo on a light UI ortheme=darkfor a light logo on a dark UI. - GET and HEAD only. Response is the image file;
Content-Typeisimage/png,image/svg+xml, etc. - 24-hour
Cache-Controlon the response. Browser/CDN caching is expected. - Fallback: if no logo is found, Logo Link returns a generated SVG monogram —
<img>tags never 404.
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 First seen · 88 lines · 57 tokens per session scan A 20e3960afc8a
logolink is a skill published in the GitHub repository context-dot-dev/cursor-plugin (4 stars, last pushed 14d ago), licensed MIT. It adds 57 tokens to every session and 933 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…