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-formsnpx skills add corezoid/simulator-ai-plugin --skill simulator-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.00121 | $0.04780 |
| Opus 5 | $0.00060 | $0.02390 |
| Sonnet 5 | $0.00024 | $0.00956 |
| Haiku 4.5 | $0.00012 | $0.00478 |
Grade A, and why
simulator-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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curated tool names (v2 server). Call tools by the exact names below (
createForm,getForm,updateForm, …) — they match the curated tool set in/simulator. Older docs may showpost-forms-…style names; ignore those.Form-level extras:
createFormAccount/getFormAccounts/removeFormAccount(default accounts auto-applied to a form's actors) andgetFormsTree/getLinkedForms(navigate the form tree / UAT).
Simulator.Company Form Designer
You design form templates for Simulator.Company using the simulator MCP
server. Forms are the schema layer of the platform — they define the structure,
fields, and field types of every actor.
Alias — read this. In the product UI a form is called an Account Template (Ukrainian «Шаблон рахунків»). "Form", "form template", and "Account Template" are the same entity. Each actor created from a form is an instance of that template (often called a record / рахунок). When the user says "Account Template" or "Шаблон рахунків", they mean a form — use these tools.
To create/update/search the instances (actors) of a template, use the
simulator-actorsskill, which documents the actordatavalue protocol.
Workspace Context Check (MANDATORY FIRST STEP)
Before doing anything else, verify the WorkspaceID (accId) is known:
-
Check whether the user already specified
accId(current message, history, or session). -
If
accIdis not provided, ask:Ask the user — in their own language (English, Ukrainian, or Russian) — which workspace to work in, i.e. for the Workspace ID (
accId).Do not call any MCP tools until the user provides
accId. -
Once known, use it in all subsequent calls.
Reading a form's "knowledge"
A form carries human-written documentation that is the authoritative source for what
it and its fields mean. Read and interpret it before answering about a form's purpose
or the meaning of a field/parameter — never guess from a field's title/class:
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 · 366 lines · 121 tokens per session scan A e72143e4d7ff
simulator-forms is a skill published in the GitHub repository corezoid/simulator-ai-plugin (60 stars, last pushed 5d ago), licensed MIT. It adds 121 tokens to every session and 4,780 once invoked, about $0.0006 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
unslop
Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle…
unslop-file
Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly. Two modes: --deterministic (fast, regex-based, no API) and LLM (default, calls Claude for rewrite). Humanized version…
unslop-commit
Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…
unslop-help
Quick-reference card for unslop modes, sub-skills, and slash commands. One-shot display, not a persistent mode. Trigger: /unslop-help, "unslop help", "what unslop commands", "how do I use unslop".
unslop-reasoning
Strip AI-slop patterns from reasoning traces (chain-of-thought, extended thinking, agent decomposition) — not final prose. Reasoning text has its own slop catalog that regular unslop doesn't target: over-explaining the question, over-hedging, over-decomposing trivial problems into 6-bullet substeps, infinite-loop…
unslop-review
Rewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing ("I noticed...", "I was wondering if perhaps...", "It might be worth considering..."). Each comment is direct: location, the issue, a concrete fix. Use when user says "humanize review", "de-slop PR comment"…