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-reactionsnpx skills add corezoid/simulator-ai-plugin --skill simulator-reactionsgit clone --depth 1 https://github.com/corezoid/simulator-ai-pluginWrote 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.
[](https://agentmods.dev/skills/corezoid/simulator-ai-plugin/simulator-reactions)<a href="https://agentmods.dev/skills/corezoid/simulator-ai-plugin/simulator-reactions"><img src="https://agentmods.dev/badge/skills/corezoid/simulator-ai-plugin/simulator-reactions.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00174 | $0.02374 |
| Opus 5 | $0.00087 | $0.01187 |
| Sonnet 5 | $0.00035 | $0.00475 |
| Haiku 4.5 | $0.00017 | $0.00237 |
Grade A, and why
simulator-reactions 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 4d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curated tool names (v2 server):
createReaction,updateReaction,deleteReaction,getReactions,getReactionsStats,markReactionsRead,getPinnedReactions,togglePinnedReaction. Call them by these exact names.
Simulator.Company Reactions Specialist
Reactions are the comments / events / approvals / ratings that live under an actor. They are themselves actors, organised as a hierarchical (threaded) tree, so a reaction can reply to another reaction.
Relationship to the other skills
simulator-actors— the actor's owndatafields (a reaction is about an actor, not its data).simulator-attachments— files attached to a reaction or actor (a reaction can carryattachments).simulator-graph— graph structure (links/layers), unrelated to reactions.
The one rule that trips everyone up: actorId vs reactionId
Every reaction path is addressed by the parent (root) actor, while the reaction's own id travels separately:
actorId(path) = the parent actor whose reaction tree you are working in.reactionId(body, on update/delete/pin) = the specific reaction to act on.parentId(on create) = the reaction you are replying to (omit for a top-level comment).
The tools expose these as distinct arguments, so you never collide the two.
Workspace context
Reactions are addressed by actorId (a UUID), so no accId is needed. Make sure you have the
target actor's UUID (use simulator-actors / searchActors to find it) before commenting.
Comment on an actor
createReaction(
type="comment", # everyday note; other types: view, rating, sign, ds, done, reject, freeze; ai = agent reply (see below)
actorId="<parent actor UUID>",
description="Looks good to me", # the comment text
notify=true) # default true; set false to post quietly
Reply in a thread — pass the parent reaction's id as parentId:
createReaction(type="comment", actorId="<parent actor UUID>",
description="Agreed", parentId="<reaction UUID being replied to>")
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.
- 4d ago First seen · 179 lines · 174 tokens per session scan A eeb832336e0a
simulator-reactions is a skill published in the GitHub repository corezoid/simulator-ai-plugin (60 stars, last pushed 7d ago), licensed MIT. It adds 174 tokens to every session and 2,374 once invoked, about $0.0009 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
crm-management
Use when an internal 101 goal must manage CRM pipelines, stages, deals, or distribution rules through the current CRM API.
estimate-management
Use when an internal 101 goal must find, read, create, or edit one or many estimates through the existing event API, including sourced or manual positions and their dates.
project-management
Use when an internal 101 goal must create or edit a project, select its customer or price list, manage project expense categories, or copy category settings from another project.
task-management
Use when an internal 101 goal must list, read, open, update, or comment on tasks, including the interactive task detail widget.
brief
This skill should be used when the user asks for "guild status", "board status", "what's the status", "show the board", "what's on the board", "project status", "show guild", "guild board", "what's happening", "brief me", "guild brief", "where are we", "what changed", "what moved since last time", "what should I work…
dashboard
This skill should be used when the user asks for "the dashboard", "guild dashboard", "open the dashboard", "show me the dashboard", "build the dashboard", "visualize the board", "the roadmap", "show the roadmap", "a visual view of the guild", "the coverage view", "the activity feed", or wants to see the guild's state…