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-actors)<a href="https://agentmods.dev/skills/corezoid/simulator-ai-plugin/simulator-actors"><img src="https://agentmods.dev/badge/skills/corezoid/simulator-ai-plugin/simulator-actors/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-actors"><img src="https://agentmods.dev/badge/skills/corezoid/simulator-ai-plugin/simulator-actors.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.00310 | $0.04568 |
| Opus 5.5 | $0.00124 | $0.01827 |
| Sonnet 5.5 | $0.00062 | $0.00914 |
| Haiku 4.5 | $0.00031 | $0.00457 |
Grade A, and why
simulator-actors 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curated tool names (v2 server):
createActor,getActor,getActorByRef,updateActor,setActorStatus,deleteActor,searchActors,filterActors,searchLayerActors,getSystemActor,getCorezoidProcesses. Call them by these exact names.
getCorezoidProcesses(actorId)is THE tool for any question about an actor's processes / functions / available API integrations — it returns the Corezoid processes shared to the actor via its access API keys (what that actor can call). If the user asks "what functions/processes does this actor have", "what can this actor call", or about the actor's shared API keys, callgetCorezoidProcesses— do not guess or use a graph-traversal tool.
getSystemActorresolves the system "twin" actor of a workspace entity — passobjType="user",objId="<userId>"to get the actor representing a user (so you can attach accounts to it or move value between users). Find theuserIdfirst withsearchUsers/getUsers. Money movement between users then goes through their twin actors' accounts via transfers — seesimulator-finance.
Simulator.Company Actor (Record) Specialist
You create and manage actors — the instances of a form template (Account
Template). An actor's field values live in its data object. Getting the data
shape right is the whole job, so this skill exists to make that mechanical.
Relationship to the other skills
simulator-formsdesigns the template (sections/fields). Read it / a form first to learn the fieldids.simulator-actors(this skill) creates/edits the records of that template.simulator-graphhandles graph structure — links, layers, FlowchartBlock diagrams. If the user wants to wire actors together or place them on a layer, defer there.simulator-financehandles accounts/transactions on actors.
Workspace Context Check (MANDATORY FIRST STEP)
Verify accId is known before any tool call. If not provided, ask:
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 · 329 lines · 310 tokens per session scan A aa264ee78051
simulator-actors is a skill published in the GitHub repository corezoid/simulator-ai-plugin (60 stars, last pushed yesterday), licensed MIT. It adds 310 tokens to every session and 4,568 once invoked, about $0.0012 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
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
gemini-api-agent-platform
Guides the usage of the Gemini API on Agent Platform with the Google Gen AI SDK for enterprise AI applications. Covers SDK usage (Python, JS/TS, Go, Java, C#), capabilities like Live API, tools, multimedia generation, caching, and batch prediction.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.