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-chatnpx skills add corezoid/simulator-ai-plugin --skill simulator-chatgit 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.00253 | $0.02728 |
| Opus 5 | $0.00127 | $0.01364 |
| Sonnet 5 | $0.00051 | $0.00546 |
| Haiku 4.5 | $0.00025 | $0.00273 |
Grade A, and why
simulator-chat 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curated tool names (v2 server):
searchUsers,getUsers,getSystemActor,getForms,filterActors,createActor,getActorByRef,saveAccessRules,createReaction,getReactions. Call them by these exact names. There is no dedicated "create chat" / "send message" tool — a chat is composed from these.
Simulator.Company Chat Specialist
In Simulator.Company a chat is an actor of the Events system form:
data.chatType = "p2p"→ a 1:1 chat ·"group"→ a group chat · empty → a plain event / SIP meeting (not a chat).- Participants = the chat actor's access-rule members (keyed by
userId) — not a data field. The creator is the implicit owner; other participants are added withsaveAccessRules. - Messages =
commentreactions posted under the chat actor.
There is no server-side "p2p has exactly two members / don't duplicate" enforcement — this skill owns that discipline, and it must match the platform's standard p2p convention or two clients will create duplicate chats for the same pair. The convention:
- Deterministic
ref=p2pConversation_<minUserId>_<maxUserId>— both participants' raw workspace userIds sorted ascending, joined with_. This is the p2p dedup key; the UI finds/reuses a chat only by this ref. title=<nickA>:p2p:<nickB>— nicks ordered by the same ascending userId sort.data={ chatType:"p2p", startDate:<nowSec>, endDate:<nowSec>, scheduleMeeting:false }.- Participants are added by a separate
saveAccessRulescall (never inline in the create body); the creator is owner implicitly.
Read
$CLAUDE_PLUGIN_ROOT/docs/entities/chats.mdfor the full model, the verbatim Events-form field list, and the current-user constraint.
Reply to the user in their own language.
Test case: "write a message to user N"
This is the canonical flow. Each step names the exact tool.
1 — Resolve user N
searchUsers(query="N") # accId defaults to the active workspace
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 · 211 lines · 253 tokens per session scan A faa21f32a189
simulator-chat is a skill published in the GitHub repository corezoid/simulator-ai-plugin (60 stars, last pushed 6d ago), licensed MIT. It adds 253 tokens to every session and 2,728 once invoked, about $0.0013 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
discuss
This skill should be used when the user says "discuss", "let's discuss", "discuss [topic]", "talk about", "let's talk about", "summarize the context", "what are we working on", "break down the topics", "what subjects do we have", "let's review the context", "recap the conversation", or any phrase asking to analyze and…
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
lark-im
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.