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/dev-lou/pixelpilot/uiux-monorepogit clone --depth 1 https://github.com/dev-lou/PixelPilotWrote 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/dev-lou/pixelpilot/uiux-monorepo)<a href="https://agentmods.dev/instructions/dev-lou/pixelpilot/uiux-monorepo"><img src="https://agentmods.dev/badge/instructions/dev-lou/pixelpilot/uiux-monorepo.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.03344 | $0.03344 |
| Opus 5 | $0.01672 | $0.01672 |
| Sonnet 5 | $0.00669 | $0.00669 |
| Haiku 4.5 | $0.00334 | $0.00334 |
Grade C, and why
PixelPilot uiux-monorepo.instructions.md scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"clean": "turbo run clean && rm -rf node_modules" How it starts
The opening of the file, as written. The whole thing — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Design System Skill
Share design tokens and components across multiple applications.
ARCHITECTURE OPTIONS
| Approach | Best For | Complexity |
|---|---|---|
| npm workspaces | Small teams, 2-3 apps | Low |
| Turborepo | Medium teams, 5+ apps | Medium |
| Nx | Large enterprise | High |
| Publishable package | External consumers | Medium |
NPM WORKSPACES (BASIC)
Folder Structure
my-monorepo/
├── package.json # Root package.json
├── packages/
│ ├── tokens/ # Design tokens
│ │ ├── package.json
│ │ ├── src/
│ │ │ ├── tokens.css
│ │ │ ├── tokens.js
│ │ │ └── index.ts
│ │ └── tsconfig.json
│ ├── ui/ # Shared components
│ │ ├── package.json
│ │ ├── src/
│ │ │ ├── Button/
│ │ │ ├── Input/
│ │ │ └── index.ts
│ │ └── tsconfig.json
│ └── utils/ # Shared utilities
│ ├── package.json
│ └── src/
└── apps/
├── web/ # Main web app
│ ├── package.json
│ └── src/
├── admin/ # Admin dashboard
│ ├── package.json
│ └── src/
└── docs/ # Documentation site
├── package.json
└── src/
Root package.json
{
"name": "my-monorepo",
"private": true,
"workspaces": [
"packages/*",
"apps/*"
],
"scripts": {
"dev": "npm run dev --workspaces --if-present",
"build": "npm run build --workspaces --if-present",
"lint": "npm run lint --workspaces --if-present",
"test": "npm run test --workspaces --if-present"
},
"devDependencies": {
"typescript": "^5.0.0"
}
}
Tokens Package
// packages/tokens/package.json
{
"name": "@myorg/tokens",
"version": "1.0.0",
"main": "dist/index.js",
"module": "dist/index.mjs",
"types": "dist/index.d.ts",
"exports": {
".": {
"import": "./dist/index.mjs",
"require": "./dist/index.js",
"types": "./dist/index.d.ts"
},
"./css": "./dist/tokens.css"
},
"files": ["dist"],
"scripts": {
"build": "tsup src/index.ts --format cjs,esm --dts && cp src/tokens.css dist/"
}
}
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.
- 3d ago First seen · 569 lines · 3,344 tokens per session scan C ca480e00f75a
PixelPilot uiux-monorepo.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 4mo ago), licensed MIT. It adds 3,344 tokens to every session, about $0.0167 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
UIX CLAUDE.md
Instructions for Deepractice/UIX, covering uix project rules, design system: lucid ui, colors, forbidden and preferred patterns.
daisyui packages.daisyui.instructions.md
Instructions for saadeghi/daisyui, covering instructions for daisyui package, files and fixing daisyui issues.
daisyui communication.instructions.md
Instructions for saadeghi/daisyui, a project described as: 🌼 🌼 🌼 🌼 🌼 The most popular, free and open-source Tailwind CSS component library.
primitives AGENTS.md
Instructions for radix-ng/primitives, covering agent guide and storybook styling.
naksha-studio copilot-instructions.md
Instructions for Adityaraj0421/naksha-studio, covering naksha design team — github copilot, activation triggers, the design team, design rules for code generation and css custom properties (always use these patterns).
lovable-boilerplate design.instructions.md
Instructions for chihebnabil/lovable-boilerplate, covering design system guidelines, critical design rules, never create, always create and core design philosophy.