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.5 | $0.00011 | $0.00150 |
| Sonnet 5.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 1mo 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.
- 1mo 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 2d ago), licensed MIT. It adds 28 tokens to every session and 376 once invoked, about $0.0001 per session on Opus 5.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
idiomatic-go
Apply Go community idioms for API and package design, error and concurrency patterns, naming (initialisms, stutter, receivers), generics vs interfaces, and Go code review — including PR or diff review, questions about "the Go way", pointer vs value receivers, channels vs mutexes, and building Go language tooling…
eclipse-license-check
Vet third-party dependencies for an Eclipse Foundation project with the Eclipse Dash License Tool — license checks, "do I need to vet X?" questions, IPLab review filing, and release IP due diligence. Use whenever the user mentions Eclipse license checking, dash-licenses, the Dash License Tool, IPLab, third-party…
go-documentation
Write idiomatic Go doc comments that render correctly on pkg.go.dev — package comments, doc.go, exported-symbol comments, testable Example functions, deprecation notices — and publish or debug modules on pkg.go.dev (pkgsite, the module proxy). Use when writing or reviewing Go documentation, or when a developer used to…
publish-vscode-extension
Publish a VS Code extension to the VS Code Marketplace and/or Open VSX Registry. Use when the user wants to publish, ship, or release a VS Code extension; audit or improve manifest, listing, or release setup; build or upload a .vsix; set up vsce or ovsx; create a marketplace publisher or Open VSX namespace; configure…
domainmodel-dsl
Read, write, and modify Domain Model DSL files (.dmodel) — datatypes, entities with inheritance and multi-valued features, and nested packages with qualified cross-references. Use when the user wants to create, edit, explain, or debug a domain model in this DSL, including resolving references across packages.
statemachine-dsl
Read, write, and modify Statemachine DSL files (.statemachine). Use when the user wants to create, edit, explain, or debug a state machine written in this textual DSL — defining states, events, commands, and transitions, or generating a machine from a description.