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.
/plugin marketplace add corezoid/simulator-ai-plugin/plugin install simulatorWrote 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/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.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00174 | $0.02374 |
| Opus 5.5 | $0.00070 | $0.00950 |
| Sonnet 5.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 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.
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.
- 1mo 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 yesterday), licensed MIT. It adds 174 tokens to every session and 2,374 once invoked, about $0.0007 per session on Opus 5.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
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
notion
Search, read, create, and update Notion pages via the Notion MCP.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
create-stories
Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.