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 instructions/glincker/thesvg/agents-mdgit clone --depth 1 https://github.com/glincker/thesvgWrote 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.
[](https://agentmods.dev/instructions/glincker/thesvg/agents-md)<a href="https://agentmods.dev/instructions/glincker/thesvg/agents-md"><img src="https://agentmods.dev/badge/instructions/glincker/thesvg/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00844 | $0.00844 |
| Opus 5 | $0.00422 | $0.00422 |
| Sonnet 5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
thesvg AGENTS.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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
thesvg - AI Review Guidelines
SVG Icon Submission Rules
Required
- Every icon directory must have
default.svg - Every SVG must have a valid
viewBoxattribute - Every SVG must contain a
<title>element with the brand name - Preferred viewBox:
0 0 24 24(match library convention) - File size must be under 50KB
- No
<script>tags, event handlers, orjavascript:URIs - No embedded raster images (
<image>with base64 data) - No
<?xml>declarations or<!DOCTYPE>preambles
Fill and Color Rules
default.svg: Must use the brand hex color asfillon<svg>root (notcurrentColor)mono.svg: Must usefill="currentColor"on<svg>rootlight.svg: Must usefill="#ffffff"or similar light colordark.svg: Must usefill="#1a1a2e"or similar dark color- Detail elements (eyes, pupils, accents) that contrast with the body must have explicit
filloverrides - they must not inherit the root fill if that makes them invisible - Stroke colors on antennae, lines, or accents must contrast with adjacent filled shapes - same-color strokes over same-color fills are invisible
- Never include a viewport-covering rectangle like
<path d="M0 0h24v24H0z"/>withoutfill="none"- this covers the entire icon
icons.json Registry
- Located at
src/data/icons.json - Entries must be alphabetically sorted by
slug - Required fields:
slug,title,aliases,hex,categories,variants,license,url hexmust not include#prefix (e.g."f43f5e"not"#f43f5e")variantsobject keys must match filenames inpublic/icons/{slug}/categoriesmust use existing category names (check existing entries)
Variant File Naming
public/icons/{slug}/
default.svg # Required - brand color
mono.svg # Recommended - inherits text color
light.svg # Optional - for dark backgrounds
dark.svg # Optional - for light backgrounds
color.svg # Optional - multi-color/gradient version
wordmark.svg # Optional - text logo
wordmarkLight.svg # Optional - light text logo
wordmarkDark.svg # Optional - dark text logo
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.
- 4d ago First seen · 75 lines · 844 tokens per session scan A 973a4f101ac7
thesvg AGENTS.md is an instructions file published in the GitHub repository glincker/thesvg (2,633 stars, last pushed 2d ago), licensed MIT. It adds 844 tokens to every session, about $0.0042 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 instructions, from other repositories
appicon AGENTS.md
AGENTS.md instructions for bolens/appicon, covering agent guidance and spec-driven changes.
png2svg AGENTS.md
Instructions for iannuttall/png2svg, covering working on png2svg, the design principle, layout gotcha, commands and testing: validate against ground truth.
png2svg CLAUDE.md
Instructions for iannuttall/png2svg, a project described as: Agent-guided PNG to SVG reconstruction for logos and icons. Clean geometry and gradients, not traced pixels.
solidworks-api-skill CLAUDE.md
Instructions for guoleizhen717/solidworks-api-skill, covering solidworks api skill repository, repository purpose, skill scope and project conventions.
q3ds-solidworks-mcp AGENTS.md
AGENTS.md instructions for zarcherlot/q3ds-solidworks-mcp, covering codex repository guidance, architecture, drawing planning and verification.
pure-admin-icons CLAUDE.md
Claude Code instructions for KeenMate/pure-admin-icons, covering claude.md, project overview, common commands, architecture and database layer (lib/database/).