logolink

A service that supplies company logos through image URLs based on a company's web domain. The image can be placed directly in a webpage, app, email, spreadsheet, or similar interface.

In plain words
What is it for?
Use it for company-logo displays, logo walls, CRM avatars, merchant icons, directories, transaction lists, and other interfaces that need logos by domain.
Why use it?
It avoids exposing a private brand-service API key in browser code and avoids parsing a larger API response just to display an image. Logos can be loaded from a CDN as raw image data.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/context-dot-dev/cursor-plugin/logolink
Any agent
npx skills add context-dot-dev/cursor-plugin --skill logolink
Clone the repo
git clone --depth 1 https://github.com/context-dot-dev/cursor-plugin

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 933 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 20e3960afc8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

skills/logolink/SKILL.md · 88 lines

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.

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 parsing brand.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

  1. Sign up at context.dev/signup if needed (free tier: 10,000 Logo Link requests/month).
  2. Copy the Public Client ID from context.dev/dashboard/logolink. Keys look like brandLL_xxx.
  3. Prefer an env var the codebase already uses, e.g. NEXT_PUBLIC_LOGOLINK_KEY or VITE_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_ID with the user's ID (or env var).
  • Replace TARGET_DOMAIN with the company domain variable (bare domain, e.g. stripe.com).
  • Optionally add theme=light for a dark logo on a light UI or theme=dark for a light logo on a dark UI.
  • GET and HEAD only. Response is the image file; Content-Type is image/png, image/svg+xml, etc.
  • 24-hour Cache-Control on the response. Browser/CDN caching is expected.
  • Fallback: if no logo is found, Logo Link returns a generated SVG monogram — <img> tags never 404.

Read the full file on GitHub · 88 lines

Changes

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.

  1. yesterday First seen · 88 lines · 57 tokens per session scan A 20e3960afc8a

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens