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/webrenew/unicon/claude-mdgit clone --depth 1 https://github.com/webrenew/uniconWrote 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/webrenew/unicon/claude-md)<a href="https://agentmods.dev/instructions/webrenew/unicon/claude-md"><img src="https://agentmods.dev/badge/instructions/webrenew/unicon/claude-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.00613 | $0.00613 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
unicon 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unicon
Just the icons you need. Zero bloat.
Browse 20,000+ icons and copy exactly what you need. Like shadcn/ui, but for icons.
- Browse once, use anywhere — Search 9 icon libraries (Lucide, Phosphor, Huge Icons, Heroicons, Tabler, Feather, Remix, Simple Icons, Iconoir)
- Copy exactly what you need — React, SVG, or JSON
- Bundle multiple icons — Export a set at once
- Zero dependencies — Paste directly into your project
- CLI —
npx @webrenew/unicon search arrow - AI integration — MCP server + IDE skills for Claude, Cursor, Windsurf, and more
- Self-hostable — See DEVELOPMENT.md
Tech Stack
- Next.js 16, React 19, TypeScript
- Supabase (auth, database, storage)
- Tailwind CSS v4
- Vercel (hosting)
Icons
NEVER use emojis in the UI. Always use icon components from @/components/icons/ui/.
All icons must be:
- Imported from
@/components/icons/ui/[icon-name].tsx - React components following the standard Unicon pattern
- Named with
Iconsuffix (e.g.,SearchIcon,PackageIcon)
Adding New Icons
Create icon components in src/components/icons/ui/ following this pattern:
import { SVGProps } from "react";
export function IconNameIcon({ className, ...props }: SVGProps<SVGSVGElement>) {
return (
<svg
xmlns="http://www.w3.org/2000/svg"
viewBox="0 0 24 24"
fill="none"
stroke="currentColor"
strokeWidth={2}
strokeLinecap="round"
strokeLinejoin="round"
aria-hidden="true"
focusable="false"
className={className}
{...props}
>
{/* SVG paths */}
</svg>
);
}
Prohibited
- No emojis in UI components
- No external icon libraries (lucide-react, heroicons, react-icons, etc.)
- No inline SVGs without extracting to a component
Code Style
- TypeScript preferred
- Functional components with hooks
- Tailwind CSS for styling
- Use
cn()from@/lib/utilsfor conditional classes - Use theme CSS variables (e.g.,
bg-background,text-foreground,border-border) — never hardcode colors
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.
- 5d ago First seen · 77 lines · 613 tokens per session scan A 8bb852a41802
unicon CLAUDE.md is an instructions file published in the GitHub repository webrenew/unicon (15 stars, last pushed 3d ago), licensed MIT. It adds 613 tokens to every session, about $0.0031 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
pure-admin-icons AGENTS.md
AGENTS.md instructions for KeenMate/pure-admin-icons, covering project guidelines, phoenix v1.8 guidelines, elixir guidelines, mix guidelines and test guidelines.
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/).
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Claude Code instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).