logodev-mcp: Instructions file for Claude Code

CLAUDE.md

logodev-mcp CLAUDE.md is an instructions file for Claude Code from pvliesdonk/logodev-mcp. It costs 5,200 tokens per session, scanned A, original, MIT.

Project instructions for building and reviewing a logo.dev MCP server, which provides company logos and brand information through an AI tool connection.

In plain words
What is it for?
It is for developing the server, using logo.dev tools, handling missing credentials, and checking that changes meet the project's requirements.
Why use it?
It gives contributors shared rules for design, project structure, API keys, error handling, and acceptance checks.

Instructions file for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: mentions CLAUDE.md.

This is pvliesdonk/logodev-mcp's own configuration. It tells Claude Code how to work on logodev-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything logodev-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pvliesdonk/logodev-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pvliesdonk/logodev-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/pvliesdonk/logodev-mcp

Made for: Claude Code.

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.

agentmods badge for logodev-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/pvliesdonk/logodev-mcp/claude-md.svg)](https://agentmods.dev/instructions/pvliesdonk/logodev-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/pvliesdonk/logodev-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pvliesdonk/logodev-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 5,200 This file is loaded in full into every session.
When invoked 5,200 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.05200 $0.05200
Opus 5 $0.02600 $0.02600
Sonnet 5 $0.01040 $0.01040
Haiku 4.5 $0.00520 $0.00520

Measured 7d ago against content hash 13cc0ae9c1ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

logodev-mcp CLAUDE.md 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 7d 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.

CLAUDE.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Logo.dev MCP

Look up company logos and brand data via the logo.dev API.

Design

Logo.dev MCP wraps the logo.dev REST + CDN API as four MCP tools gated by two API key types:

  • get_logo — fetches a company logo image from the logo.dev CDN. Requires LOGODEV_MCP_PUBLISHABLE_KEY (pk_…).
  • search_brands — resolves a brand/company name to candidate domains. Requires LOGODEV_MCP_SECRET_KEY (sk_…).
  • describe_company — returns structured company data (name, description, colours, socials) for a domain. Requires LOGODEV_MCP_SECRET_KEY.
  • get_brand — returns the full brand profile (logo, brandmark, banners, colours, description) for a domain. Requires LOGODEV_MCP_SECRET_KEY.

Tools for a missing key are not registered at all (graceful degradation) — the MCP client only sees tools that can actually execute. If neither key is set, no API tools are registered and a warning is logged.

Errors from the logo.dev API are caught as LogoDevError and returned to the caller as a plain text message string rather than raising a server exception.

Project Structure

src/logodev_mcp/
  domain.py      # Service class + LogoDevError — pure Python, no FastMCP imports
  tools.py       # FastMCP tool registrations; calls into domain.py
  config.py      # ProjectConfig with publishable_key + secret_key fields
  _server_deps.py# FastMCP DI provider: get_service() → Service instance
  server.py      # make_server() — wires config, tools, and server info
tests/
  test_tools.py  # Tool registration gating + tool call integration tests (respx)
  test_domain.py # Domain-layer unit tests (respx, no FastMCP)

Conventions

  • Python 3.11+
  • uv for package management, ruff for linting/formatting (line length 88)
  • hatchling build backend
  • Conventional commits: feat:, fix:, docs:, refactor:, test:, chore:
  • Google-style docstrings on all public functions
  • logging.getLogger(__name__) throughout, no print()
  • Type hints everywhere
  • Tests: pytest with fixtures in tests/fixtures/

Read the full file on GitHub · 223 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. 7d ago First seen · 223 lines · 5,200 tokens per session scan A 13cc0ae9c1ae

Subscribe to this mod's changes

logodev-mcp CLAUDE.md is an instructions file published in the GitHub repository pvliesdonk/logodev-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 5,200 tokens to every session, about $0.0260 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 instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens