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/forge-space/ui-mcp/claude-mdgit clone --depth 1 https://github.com/Forge-Space/ui-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/forge-space/ui-mcp/claude-md)<a href="https://agentmods.dev/instructions/forge-space/ui-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/forge-space/ui-mcp/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.00760 | $0.00760 |
| Opus 5 | $0.00380 | $0.00380 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
ui-mcp 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 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Siza MCP
Quick Reference
NODE_OPTIONS=--experimental-vm-modules npm run build
NODE_OPTIONS=--experimental-vm-modules npm test
npm run registry:check # validate server.json ↔ package.json
npm run validate:all # lint + format + tsc + test + build
Project
- Thin MCP protocol adapter for AI-powered UI/backend code generation
- All AI/ML, generators, registry, feedback, and quality code lives in
@forgespace/siza-gen - GitHub: Forge-Space/ui-mcp, default branch:
main - npm:
@forgespace/ui-mcp, binary:forgespace-ui-mcp - Bundle: ~403 KB (tools, services, resources only)
Architecture
@forgespace/ui-mcp (this repo) @forgespace/siza-gen
├── src/index.ts (MCP server) ├── ml/ (embeddings, quality, training)
├── tools/ (33 tool files) ├── generators/ (react, vue, angular, svelte, html)
├── services/ (figma, analysis) ├── registry/ (502 snippets, compositions, packs)
├── resources/ (MCP resources) ├── feedback/ (self-learning, pattern promotion)
└── lib/ (browser, image) └── quality/ (anti-generic rules, diversity)
Stack
- TypeScript, Node 22, Jest ESM, tsup, pino
NODE_OPTIONS=--experimental-vm-modulesrequired for Jest
Build/Test Pipeline
npm run buildbeforenpm test- Pre-push hook: lint → format:check → tsc → test → build
- 45 test suites, 529 tests (tool-level + integration)
- siza-gen has 343 additional tests for AI/registry internals
Distribution
server.json— MCP Registry metadata (io.github.forge-space/ui-mcp)publish.yml— tag-driven: pushv*→ npm publish + MCP Registry + GitHub releasemcp-registry-status.yml— weekly tracking issue with npm/registry driftregistry:check— pre-publish validation (server.json ↔ package.json alignment)
What Stays Here
src/tools/— 33 tool files (schema + handler glue)src/services/— Figma, analysis, generation, design servicessrc/resources/— MCP resource providerssrc/lib/— browser-scraper, design-extractor, figma-client, image-analyzer, image-renderer, pattern-detector, prototype-builder, style-audit, tailwind-mapper, templates/scripts/— registry-check.mjs, mcp-registry-status.mjs
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 · 71 lines · 760 tokens per session scan A 1cfd7977ffdd
ui-mcp CLAUDE.md is an instructions file published in the GitHub repository Forge-Space/ui-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 760 tokens to every session, about $0.0038 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
angular AGENTS.md
AGENTS.md instructions for angular/angular, covering environment, key documentation, testing and pull requests.
promptscript typescript.instructions.md
Instructions for mrwogu/promptscript, a project described as: Prompt-as-Code for Enterprise AI. Standardize, audit, and deploy instructions across any AI coding assistant.
primitives angular.instructions.md
Instructions for radix-ng/primitives, covering typescript best practices, angular best practices, components, state management and templates.
lamina typescript.instructions.md
Guidelines for using modern TypeScript features (v5.0-v5.8).
openbridge-webcomponents AGENTS.md
AGENTS.md instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering agents.md — universal ai agent instructions, 1. repository overview, source directory layout, 2. coding standards and comments.
anilist-mcp-server AGENTS.md
AGENTS.md instructions for Grinv/anilist-mcp-server, covering agents.md, project shape, why this server exists, commands and conventions.