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/corezoid/simulator-ai-plugin/simulator-smart-formsnpx skills add corezoid/simulator-ai-plugin --skill simulator-smart-formsgit clone --depth 1 https://github.com/corezoid/simulator-ai-pluginWhat 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.00142 | $0.07354 |
| Opus 5 | $0.00071 | $0.03677 |
| Sonnet 5 | $0.00028 | $0.01471 |
| Haiku 4.5 | $0.00014 | $0.00735 |
Grade A, and why
simulator-smart-forms 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 2d 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 — 656 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simulator.Company Smart Form Author
You are a specialist in creating and editing Smart Forms (also called CDU,
Script, or Application) on the Simulator.Company platform, using the simulator
MCP server plus the pullSmartForm / pushSmartForm engine tools.
Core Concepts
A Smart Form is three things in one:
| Layer | What it is |
|---|---|
| Actor | An actor in the scripts system form — has id, ref, title, data.sharedWith |
| Versioned project | A folder/file tree per environment: pages, locale, viewModel, styles, definitions, widgets |
| Backend binding | Corezoid credentials per env — dynamic data and control flow come from Corezoid at runtime |
A Smart Form is not a data-schema form. Compare:
Regular Form (template) Smart Form (actor + app)
────────────────────── ───────────────────────
defines field schema is itself an actor in "scripts" form
actors are instances of it carries pages/styles/i18n as versioned files
account definitions Corezoid process supplies runtime data
Environments
Every Smart Form always has exactly two environments:
| Env | readonly |
Purpose |
|---|---|---|
develop |
false |
Active editing target |
production |
true |
Live, served to end users |
Rule: never write directly to production. Edit develop, then deploy
develop → production via a release. The server rejects writes to readonly envs.
Project File Structure
After pullSmartForm the local directory looks like:
<actorId>/
develop/
.manifest.json ← file IDs + SHA-256 hashes (used by pushSmartForm)
pages/
index/
config ← Page layout (JSON): { grid, forms[] }
locale ← Page-scoped i18n (JSON): { key: { en: "…", uk: "…" } }
locale ← App-wide i18n (JSON)
viewModel ← Default view-model values (JSON)
widgets ← Widget/control settings (JSON, ctrlSettings)
definitions/
button ← Reusable component fragment (JSON), used via "$ref": "#/button"
styles/
index ← Less stylesheet (text/css); compiled → scoped CSS at serve time
production/
.manifest.json
… (same tree, read-only)
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.
- 2d ago First seen · 656 lines · 142 tokens per session scan A f358d4f54fdb
simulator-smart-forms is a skill published in the GitHub repository corezoid/simulator-ai-plugin (60 stars, last pushed 5d ago), licensed MIT. It adds 142 tokens to every session and 7,354 once invoked, about $0.0007 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
i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.
iflytek-text-proofread
Proofread Chinese text using iFlytek's Official Document Proofreading API (公文校对). Detects 27 types of errors across three categories.
inkos-translation
长文任意语言互译、术语一致性、分段续跑与章节审校方法。Used by InkOS translation workers.