simulator-styles

simulator-styles is a skill for Claude Code from corezoid/simulator-ai-plugin. It costs 333 tokens per session (12,335 once invoked), scanned C, original, MIT.

A styling guide for Simulator.Company Smart Forms, which are configurable web forms and apps built from layouts, fields, and components.

In plain words
What is it for?
Writing Less or CSS for themes, responsive layouts, sections, controls, component redesigns, reusable styles, and design-system patterns.
Why use it?
It helps developers change the appearance of an existing form without mixing visual work with its data structure, page layout, or backend logic.

Skill for Claude Code

Written for Claude Code: $CLAUDE_PLUGIN_ROOT variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the simulator plugin — 21 skills, 1 MCP server shipped together

Good fit Writing Less or CSS for themes, responsive layouts, sections, controls, component redesigns, reusable styles, and design-system patterns.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add corezoid/simulator-ai-plugin
Claude Code
/plugin install simulator

Made for: Claude Code.

Or install simulator, the plugin that ships this one along with the rest of its 21 skills, 1 MCP server.

Wrote 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.

agentmods badge for simulator-styles

README.md
[![agentmods](https://agentmods.dev/badge/skills/corezoid/simulator-ai-plugin/simulator-styles/github.svg)](https://agentmods.dev/skills/corezoid/simulator-ai-plugin/simulator-styles)
Your own site
<a href="https://agentmods.dev/skills/corezoid/simulator-ai-plugin/simulator-styles"><img src="https://agentmods.dev/badge/skills/corezoid/simulator-ai-plugin/simulator-styles/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.

agentmods 80×15 button for simulator-styles

Your own site · 80×15
<a href="https://agentmods.dev/skills/corezoid/simulator-ai-plugin/simulator-styles"><img src="https://agentmods.dev/badge/skills/corezoid/simulator-ai-plugin/simulator-styles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 333 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 12,335 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00333 $0.12335
Opus 5.5 $0.00133 $0.04934
Sonnet 5.5 $0.00067 $0.02467
Haiku 4.5 $0.00033 $0.01234

Measured 1mo ago against content hash a5de75d9190a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

simulator-styles scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .lesscheck && mkdir .lesscheck
plugins/simulator/skills/simulator-styles/SKILL.md · 589 lines

How it starts

The opening of the file, as written. The whole thing — 589 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Simulator.Company Smart Form STYLING specialist

You author and apply CSS/Less styles for Smart Forms (CDU / Script apps) on Simulator.Company. Your domain is the style / styles/ layer — themes, layout, component re-skinning, reusable patterns, responsive and design-system approaches.

This skill is built on patterns reverse-engineered from real production Smart Forms; the recipes below are taken from live Less, not invented.


Scope — what this skill owns (and what it does NOT)

Concern Skill
Styling: style / styles/*, pages/<id>/style, styleClass, themes, Less this skill
Form template (data fields / Account Template) simulator-forms
Page layout JSON (pages/<id>/config: grid/forms/sections/items), viewModel, locale simulator-smart-forms
Backend logic (Corezoid /get /send, dynamic viewModel, changes[]) simulator-smart-forms-logic
Generating a whole app (pages + middleware) from existing Corezoid processes simulator-app-generator

You reuse the Smart Form engine tools (pullSmartForm, pushSmartForm, deploySmartForm, file-history/rollback) — you do not introduce new platform behaviour. When the user needs a new form/page first, defer to simulator-smart-forms; you come in to make it look right. To attach a styleClass to a component you may need a one-line edit to pages/<id>/config — that's in scope (it's the binding), but designing the layout itself belongs to simulator-smart-forms.


How Smart Form styling works (the model)

  1. One Less stylesheet, compiled per save, scoped to .cdu-page. Whatever you write is wrapped in .cdu-page { … } at serve time, so & = the page root and your styles can't leak out. Less syntax (variables, mixins, @import, functions, maps, guards, each()) is fully supported.
  2. File organization — and where each rule goes. Two layouts compile identically; prefer the modular styles/ folder for anything non-trivial:
    • Legacy single file — a root style file holds everything (big forms: Admin Panel, CMS, LMS).
    • Modular styles/ — styles/index is the entry point and mainly just @imports partials, in cascade order:
      // styles/index — the entry/manifest; imports in cascade order
      @import "colors_fonts";   // tokens FIRST (everything below + page styles inherit them)
      @import "init_styles";    // then platform resets + project-wide component defaults
      // … any other shared partials (mixins, shared components) …
      
    • Page styles — pages/<id>/style is auto-appended after the main stylesheet (so it wins the cascade) and inherits all root variables/mixins (no @import needed). The platform saves it as text/css automatically. It is for that page's exceptions only.

Read the full file on GitHub · 589 lines

Changes

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.

  1. 1mo ago First seen · 589 lines · 333 tokens per session scan C a5de75d9190a

Subscribe to this mod's changes

simulator-styles is a skill published in the GitHub repository corezoid/simulator-ai-plugin (60 stars, last pushed yesterday), licensed MIT. It adds 333 tokens to every session and 12,335 once invoked, about $0.0013 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.