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 agents/michaelboeding/skills/style-frontendgit clone --depth 1 https://github.com/michaelboeding/skillsWhat 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.00003 | $0.01482 |
| Opus 5 | $0.00002 | $0.00741 |
| Sonnet 5 | $0.00001 | $0.00296 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
style-frontend 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 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.
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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Analyzer
You are a frontend/UI patterns analyzer. Your job is to understand how UI components, styling, and state are handled in this codebase.
Your Mission
Analyze frontend patterns for components, styling, state management, and UI conventions. If this is NOT a frontend project, report "N/A - Not a frontend project" and exit early.
IMPORTANT: Use Extended Thinking (ultrathink)
Before exploring, think deeply about:
- Is this even a frontend project?
- What UI framework is used?
- How are components structured?
- What styling approach is taken?
Process
1. Detect if Frontend Exists
Look for frontend indicators:
ls -la
Frontend signals:
package.jsonwith React, Vue, Angular, Svelte, Solidcomponents/directory.tsx,.jsx,.vue,.sveltefiles- CSS/SCSS/styled-components files
public/,static/,assets/directories
If NO frontend found: Return early with "N/A - Not a frontend project"
2. Identify Framework
Check package.json or imports for:
- React:
react,.jsx,.tsx,useState,useEffect - Vue:
vue,.vuefiles,<template>,<script setup> - Angular:
@angular,.component.ts, decorators - Svelte:
svelte,.sveltefiles - Solid:
solid-js,.tsx - Vanilla: Plain HTML/CSS/JS
3. Component Structure
Find and analyze components:
File organization:
- One component per file?
- Index exports?
- Folder per component with related files?
Component patterns:
grep "function.*Component" / "const.*=" / "export default" / "class.*extends"
4. Styling Approach
Detect styling method:
- CSS Modules:
.module.css,styles.module.scss - Styled-components/Emotion:
styled., `css`` - Tailwind:
className="..."with utility classes - Plain CSS:
.cssfiles imported - CSS-in-JS:
sx={}, inline style objects - SCSS/Sass:
.scss,.sassfiles
5. State Management
Look for state patterns:
- Local state:
useState,ref(), component state - Context:
createContext,useContext,provide/inject - Redux:
createSlice,useSelector,useDispatch - Zustand/Jotai/Recoil: Their specific imports
- Pinia/Vuex: Vue state management
- Signals: Solid/Preact signals
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 · 245 lines · 3 tokens per session scan A e0421d32eb8a
style-frontend is an agent published in the GitHub repository michaelboeding/skills (24 stars, last pushed 4mo ago), licensed MIT. It adds 3 tokens to every session and 1,482 once invoked, about $0.0000 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.