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 skills add niels-emmer/myace --skill component-conventionsgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/skills/niels-emmer/myace/component-conventions)<a href="https://agentmods.dev/skills/niels-emmer/myace/component-conventions"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/component-conventions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/niels-emmer/myace/component-conventions"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/component-conventions.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.00376 |
| Opus 5 | $0.00014 | $0.00188 |
| Sonnet 5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
Component Conventions 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.
What it actually says
Purpose
Consistent component sizing, naming, and structure across the codebase.
When to use it
Adding a new component, deciding whether to split one, or deciding where state should live.
Composition
- Default to small components with one clear job. Signal of too-big: mixes data fetching + layout + business logic + presentation.
- Don't extract single-use components prematurely — splitting adds indirection without benefit.
- Extract when: reused in >1 place, represents a distinct nameable concept, or measurably simplifies the parent.
Naming
- Name for what the component represents (
UserAvatar, notRoundImageWithBorder). - Match the project's existing casing and file-naming convention.
- Keep file name and exported name in sync.
Prop design
- Pass only what the component needs — avoid passing entire data objects when two fields suffice.
- Prefer explicit typed props over a generic
data/configblob. - Use
variant/sizeenums over piles of independent booleans.
State locality
- Keep state in the component that owns it.
- Lift only to the nearest common ancestor when multiple components genuinely share the value.
- Use global state only for app-wide data (auth, theme).
Expected output
A component with one clear responsibility, purpose-based name, minimal typed props, and state as local as sharing requirements allow.
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 · 44 lines · 28 tokens per session scan A 22cb44430f97
Component Conventions is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 376 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…
loom-react
Modern client-side React development patterns.
loom-accessibility
Web accessibility patterns, WCAG compliance, and inclusive design.
tanstack-integration
Find opportunities to improve web application code using TanStack libraries (Query, Table, Form, Router, etc.). Avoid man-with-hammer syndrome by applying TanStack after vanilla implementation works.
ui-ux-polish
Iterative UI/UX polishing workflow for web applications. The exact prompt and methodology for achieving Stripe-level visual polish through multiple passes.
frontend-architecture
Component architecture, design patterns, state management strategies, module systems, build tools, and scalable application structure.