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/drn/dots/logonpx skills add drn/dots --skill logogit clone --depth 1 https://github.com/drn/dotsWhat 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.00023 | $0.03356 |
| Opus 5 | $0.00012 | $0.01678 |
| Sonnet 5 | $0.00005 | $0.00671 |
| Haiku 4.5 | $0.00002 | $0.00336 |
Grade A, and why
logo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logo Generation
Generate SVG logo alternatives for a project, then present them in a side-by-side comparison page for review.
Arguments
$ARGUMENTS- Description of the logo concept, style direction, or project name
Instructions
You are generating SVG logo alternatives and a visual comparison page. Your goal is to produce 6 distinct design directions so the user can pick and refine.
Step 1: Understand the Brief
Determine what the logo should communicate:
- Project name — What is the logo for?
- Core concept — What metaphor or visual idea? (e.g., "forge + AI agents", "speed + reliability")
- Style direction — Modern/minimal, geometric, organic, playful, corporate?
- Color palette — Dark background? Brand colors? Warm/cool?
- Shape — Circle, rounded rect, hexagon, freeform?
- Existing logo — Is there a current logo to improve on? Read it first.
If unclear, ask the user before generating.
Step 2: Design 6 Alternatives
Create 6 meaningfully different SVG logo files. Each should explore a distinct visual direction:
| # | Direction | Color | What to Try |
|---|---|---|---|
| 1 | Minimal | Amber/Gold | Strip to the essential mark. One shape, one gradient. App icon clean. |
| 2 | Geometric | Cyan/Teal | Low-poly, faceted, angular. Crystal/tech aesthetic. |
| 3 | Organic | Violet/Purple | Flowing curves, natural forms. Warmth and craft. |
| 4 | Typographic | Emerald/Green | Lettermark or monogram. The initial letter as hero. |
| 5 | Conceptual | Rose/Pink | Symbolic/metaphorical. Combine two ideas into one mark (e.g., flame + orbits). |
| 6 | Sci-fi | Blue/Indigo | Orbital, atomic, or space-inspired. Tech gravitas. |
CRITICAL: No text in logos. Never use <text> elements, letters, words, or typographic marks in the SVG logos. Every logo must be purely symbolic — shapes, icons, and abstract marks only. Text/wordmarks are added separately by the user if needed.
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 · 198 lines · 23 tokens per session scan A c37590567ff5
logo is a skill published in the GitHub repository drn/dots (23 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 3,356 once invoked, about $0.0001 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-30.
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…