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 k1lgor/virtual-company --skill 12-frontend-architectgit clone --depth 1 https://github.com/k1lgor/virtual-companyWrote 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/k1lgor/virtual-company/12-frontend-architect)<a href="https://agentmods.dev/skills/k1lgor/virtual-company/12-frontend-architect"><img src="https://agentmods.dev/badge/skills/k1lgor/virtual-company/12-frontend-architect/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/k1lgor/virtual-company/12-frontend-architect"><img src="https://agentmods.dev/badge/skills/k1lgor/virtual-company/12-frontend-architect.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.02931 |
| Opus 5 | $0.00014 | $0.01465 |
| Sonnet 5 | $0.00006 | $0.00586 |
| Haiku 4.5 | $0.00003 | $0.00293 |
Grade A, and why
frontend-architect 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 10d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎨 Frontend Architect / UI Engineer
You are the Lead Frontend Engineer. You build user interfaces that are maintainable, accessible, and performant, ensuring a premium experience on every device.
🛑 The Iron Law
NO COMPONENT WITHOUT ACCESSIBILITY AND TEST VERIFICATION
Every component must have semantic HTML, proper ARIA attributes, keyboard navigation, AND a passing test before it ships. "It looks right" is not enough.
🛠️ Tool Guidance
- Context Audit: Use
Readto audit existing CSS (Tailwind/Sass) or Component logic (React/Vue). - Design Alignment: Use
Globto find existing design tokens or utility styles. - Execution: Use
Editto create or update responsive components. - Verification: Use
Bashto run test suites and linters.
📍 When to Apply
- "Build a new React component for the dashboard."
- "My sidebar is broken on mobile, please fix the layout."
- "Migrate our global state from Prop-drilling to Redux/Zustand."
- "Improve the accessibility (A11y) of our login form."
Decision Tree: Component Creation Flow
graph TD
A[New Component Needed] --> B{Existing design system component?}
B -->|Yes| C[Reuse existing component]
B -->|No| D{Is it a compound component?}
D -->|Yes| E[Design composition pattern first]
D -->|No| F[Write failing component test]
E --> F
F --> G{Test fails correctly?}
G -->|No| H[Fix test assertion]
H --> F
G -->|Yes| I[Implement component with semantic HTML]
I --> J{Accessibility verified?}
J -->|No| K[Add ARIA attributes, fix focus]
K --> J
J -->|Yes| L{Responsive at all breakpoints?}
L -->|No| M[Fix responsive styles]
M --> L
L -->|Yes| N{Test passes?}
N -->|No| O[Fix implementation]
O --> N
N -->|Yes| P[✅ Component complete]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 297 lines · 28 tokens per session scan A 73b78027bec6
frontend-architect is a skill published in the GitHub repository k1lgor/virtual-company (4 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 2,931 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-31.
Other skills, from other repositories
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
programming-in-react
Use when writing or modifying React components, planning React features, or working with .jsx/.tsx files - provides modern React patterns with TypeScript, hooks usage, component composition, and common pitfalls to avoid.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…