Borrowing it
Nothing to install: this file belongs to ErneG/svgo-jsx-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/ErneG/svgo-jsx-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/ErneG/svgo-jsx-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/erneg/svgo-jsx-mcp/agents-md)<a href="https://agentmods.dev/instructions/erneg/svgo-jsx-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/erneg/svgo-jsx-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.00781 | $0.00781 |
| Opus 5 | $0.00391 | $0.00391 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
svgo-jsx-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 7d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - SVGO JSX MCP
Project Context
SVGO JSX is an SVG optimization service with JSX-compatible camelCase attribute conversion. It provides:
- A web UI for manual SVG optimization
- An MCP (Model Context Protocol) server for AI assistants
- REST API for programmatic access
- Admin dashboard for API key management and statistics
Architecture
- Monorepo using pnpm workspaces
- packages/web: Next.js 16 app (App Router) with React 19
- packages/api: MCP server implementation
- packages/shared: Shared utilities and types
Tech Stack
- Framework: Next.js 16.x with App Router
- Database: PostgreSQL via Prisma ORM
- Auth: Better Auth
- State Management: TanStack Query (React Query)
- Forms: TanStack Form with Zod validation
- UI Components: shadcn/ui with Radix primitives
- Styling: Tailwind CSS v4
- Charts: Recharts
- Testing: Vitest with React Testing Library
Code Quality Standards
This is production code deployed to users. Maintain high standards:
TypeScript
- Strict mode enabled
- No
anytypes without explicit justification - Proper null handling with optional chaining and nullish coalescing
React Patterns
- Use Server Components by default, "use client" only when needed
- TanStack Query for all data fetching in client components
- Proper loading and error states for async operations
- Always handle edge cases (empty data, loading, errors)
API Routes
- Validate authentication with
auth.api.getSession() - Return proper HTTP status codes
- Handle BigInt serialization (convert to string for JSON)
- Use proper error responses with meaningful messages
Database
- Use Prisma for all database access
- Prefer computed queries over denormalized aggregates when data freshness matters
- Index fields used in WHERE clauses
Testing Requirements
- API routes should have endpoint existence tests
- Critical business logic should have unit tests
- Run
pnpm testbefore committing
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.
- 7d ago First seen · 106 lines · 781 tokens per session scan A 06ffaa36137f
svgo-jsx-mcp AGENTS.md is an instructions file published in the GitHub repository ErneG/svgo-jsx-mcp (0 stars, last pushed 7mo ago), licensed MIT. It adds 781 tokens to every session, about $0.0039 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 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.