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/sacredvoid/skillkit/logo-generatornpx skills add sacredvoid/skillkit --skill logo-generatorgit clone --depth 1 https://github.com/sacredvoid/skillkitWhat 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.00063 | $0.03513 |
| Opus 5 | $0.00032 | $0.01757 |
| Sonnet 5 | $0.00013 | $0.00703 |
| Haiku 4.5 | $0.00006 | $0.00351 |
Grade A, and why
logo-generator 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 2d 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logo Generator
Generate custom SVG logos through adaptive brainstorming, then export a full brand asset kit.
First-Run Setup
Check if sharp is installed in the skill's scripts directory:
[ -d ~/.claude/skills/logo-generator/scripts/node_modules/sharp ] || (cd ~/.claude/skills/logo-generator/scripts && npm install)
Run this silently at the start of every invocation. If it fails, warn the user and continue — the script has a macOS qlmanage+sips fallback.
Phase 1: Context Scan
Automatically scan the current working directory for branding signals. Do NOT ask the user for any of this — just read it.
What to scan
| Source | What to extract |
|---|---|
package.json / Cargo.toml / pyproject.toml |
Project name, description, keywords |
README.md / README |
Project name, tagline, description |
CLAUDE.md |
Project conventions, tech stack |
tailwind.config.* / theme.config.* |
Brand colors, font choices |
*.css (first 3 files) |
CSS custom properties with color values |
public/ / assets/ / static/ |
Existing logos, favicons, brand images |
.svg / .png files in root |
Existing logo files |
manifest.json / site.webmanifest |
App name, theme color |
How to scan
# Quick scan — run these and read results
ls package.json README.md CLAUDE.md tailwind.config.* manifest.json site.webmanifest 2>/dev/null
Use Glob for: **/*.svg, **/favicon*, **/logo*
Use Grep for: --theme-color, --primary, --brand, color: in CSS files
Build a context summary
After scanning, build an internal summary:
CONTEXT:
name: [found or "unknown"]
description: [found or "none"]
colors_found: [list of hex codes with where they came from]
existing_logos: [paths to any existing logo/favicon files]
tech_stack: [detected from config files]
has_branding: [yes/partial/no]
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 372 lines · 63 tokens per session scan A 5d2d5f8a085e
logo-generator is a skill published in the GitHub repository sacredvoid/skillkit (10 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 3,513 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
image-fetcher
Fetch relevant, high-quality, free-to-use images from the web. Accepts a description/query, or scans the current directory for context. Sources from Unsplash, Pexels, and Pixabay APIs (if keys configured) with a zero-config WebSearch fallback.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
playwright-e2e-testing
Author and maintain versioned Playwright (@playwright/test) TypeScript UI specs for browser user flows. Use when asked to create, run, debug, or refactor E2E tests, form/navigation/auth flows, responsive checks, UI mocking, fixtures, Page Objects, or visual comparisons. Use api-testing for standalone REST/GraphQL…
webapp-selenium-testing
Author and maintain versioned Selenium WebDriver tests with Java and JUnit 5. Use for creating, debugging, or running Selenium specs, implementing Page Objects, handling explicit waits, capturing screenshots, or setting up Maven test projects. Supports Chrome, Firefox, and Edge. Keywords: Selenium WebDriver, Java…
fetch-url-as-markdown
Fetch a web page (URL) and return clean Markdown via local trafilatura, with Exa MCP as a fallback for JS-rendered or anti-bot pages. Use when the user asks to read, fetch, scrape, summarize, or quote a URL — prefer this over the built-in WebFetch tool. Don't use for binary files (PDFs, images, archives) or for…
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…