Borrowing it
Nothing to install: this file belongs to Remix-Design/RemixIcon-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.
curl -O https://raw.githubusercontent.com/Remix-Design/RemixIcon-MCP/main/AGENTS.mdgit clone --depth 1 https://github.com/Remix-Design/RemixIcon-MCPWrote 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/remix-design/remixicon-mcp/agents-md)<a href="https://agentmods.dev/instructions/remix-design/remixicon-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/remix-design/remixicon-mcp/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.1 | $0.00571 | $0.00571 |
| Opus 5 | $0.00285 | $0.00285 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
RemixIcon-MCP 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 8d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Architecture & Dependencies
This MCP server follows strict Clean Architecture: interface/ only handles transport, infrastructure/ adapts data sources, application/ orchestrates use cases, and domain/ owns business rules. Respect the dependency rule by importing inward only; new adapters belong under infrastructure/ and must receive dependencies via constructors. bootstrap/ wires modules together, so extend it when registering additional repositories or validators. The shared icon tags live in data/tags.json; treat it as read-only at runtime.
Project Structure & Module Organization
Source lives in src/ with TypeScript entrypoint index.ts. Tests mirror the layers inside tests/application/ and tests/domain/, and any infrastructure tests should sit under tests/infrastructure/ when added. Keep assets and fixtures co-located with their layer to avoid leaking implementation details across boundaries.
Build, Test & Verification Commands
Use pnpm consistently:
pnpm install # Restore dependencies
pnpm typecheck # Run tsc --noEmit for strict types
pnpm test # Execute Vitest suites
pnpm lint # Apply Biome lint autofixes
pnpm format # Format sources with Biome
Run the full sequence before pushing or cutting a release branch.
Coding Style & Naming Conventions
Biome enforces two-space indentation, double quotes, and organized imports. Prefer descriptive names like SearchIconsUseCase over abbreviations, and keep functions under 50 lines. Expose domain types via explicit TypeScript exports and document “why” decisions with brief comments when logic is non-obvious. Avoid hardcoded secrets and keep configuration in Bootstrap wiring.
Testing Workflow
Follow mandatory TDD: add a failing *.test.ts in tests/<layer>/ before touching implementation. Use Vitest describe blocks to mirror use cases, and include coverage for error paths such as invalid keywords or missing icon matches. For quick validation, run pnpm test --runInBand locally, then ensure pnpm test passes without flags.
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.
- 8d ago First seen · 31 lines · 571 tokens per session scan A 5765ba4b0544
RemixIcon-MCP AGENTS.md is an instructions file published in the GitHub repository Remix-Design/RemixIcon-MCP (93 stars, last pushed 1mo ago), licensed MIT. It adds 571 tokens to every session, about $0.0029 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
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.
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.
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).
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).
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.
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.