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 skills/ea-toolkit/architecture-catalog/scaffold-componentnpx skills add ea-toolkit/architecture-catalog --skill scaffold-componentgit clone --depth 1 https://github.com/ea-toolkit/architecture-catalogWrote 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/ea-toolkit/architecture-catalog/scaffold-component)<a href="https://agentmods.dev/skills/ea-toolkit/architecture-catalog/scaffold-component"><img src="https://agentmods.dev/badge/skills/ea-toolkit/architecture-catalog/scaffold-component.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.00018 | $0.00720 |
| Opus 5 | $0.00009 | $0.00360 |
| Sonnet 5 | $0.00004 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
scaffold-component 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Component
Scaffold a new React component in catalog-ui/src/components/ with a co-located test file.
Arguments
$ARGUMENTS should be a PascalCase component name (e.g., CapabilityHeatmap, DomainSummaryCard).
If no argument is provided, ask the user for a component name.
Workflow
-
Parse component name from
$ARGUMENTS. Ensure PascalCase. -
Determine target directory based on component purpose:
- Graph/visualization component →
catalog-ui/src/components/graphs/ - Diagram viewer →
catalog-ui/src/components/ - Layout/navigation →
catalog-ui/src/components/(or subdirectory if pattern exists) - General →
catalog-ui/src/components/ - Ask the user if unclear.
- Graph/visualization component →
-
Read existing context:
- Read
models/registry-mapping.yamlif the component will render registry data. - Read an existing similar component in the target directory for pattern reference.
- Read
catalog-ui/src/lib/types.tsfor TypeScript interfaces.
- Read
-
Create component file (
ComponentName.tsx):- Export Props interface:
export interface ComponentNameProps { ... } - Named export (not default):
export const ComponentName: React.FC<ComponentNameProps> = ... - CSS via
--ec-*variables (never inline styles) - Semantic HTML (nav, main, section, article — not div for everything)
- Accessible: aria labels on interactive elements
- If rendering registry data: drive all behavior from schema properties (graph_rank, layer, icon), never from type name strings
- Export Props interface:
-
Create test file (
ComponentName.test.tsxin same directory or__tests__/):- At minimum: one render/smoke test + one behavioral test
- Use Vitest (
import { describe, it, expect } from 'vitest') - Mock external dependencies (ReactFlow, data loaders) if needed
-
Verify types:
cd catalog-ui && npx tsc --noEmit
Template Pattern
// ComponentName.tsx
import type React from 'react';
export interface ComponentNameProps {
// Define props here
}
export const ComponentName: React.FC<ComponentNameProps> = (props) => {
return (
<section aria-label="Component description">
{/* Component content */}
</section>
);
};
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 · 92 lines · 18 tokens per session scan A c3f066935752
scaffold-component is a skill published in the GitHub repository ea-toolkit/architecture-catalog (38 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 720 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-08-30.
Other skills, from other repositories
chrome-ext-ui-react
This skill should be used when building React UI for Chrome extensions or when the user asks about UI patterns in extensions. Trigger when: "React in extension", "extension popup React", "side panel React", "Shadow DOM React", "content script UI", "createShadowRootUi", "extension accessibility", "rem to px extension"…
astro-docs
Comprehensive Astro framework reference covering components, pages, layouts, routing, styling, markdown, content collections, islands architecture, server islands, actions, middleware, endpoints, data fetching, view transitions, integrations, deployment, environment variables, imports, images, fonts, i18n, sessions…
astro-expert
Astro framework expertise — islands architecture, SSR/hybrid modes, React integration, performance, and production-ready frontend scaffolding.
react19
React 19 conventions in ONE sites — client islands, @oneie/react hooks, no useEffect for ONE data. Invoke when editing .tsx components.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.