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-graphnpx skills add corezoid/simulator-ai-plugin --skill simulator-graphgit 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.00361 | $0.08296 |
| Opus 5 | $0.00180 | $0.04148 |
| Sonnet 5 | $0.00072 | $0.01659 |
| Haiku 4.5 | $0.00036 | $0.00830 |
Grade A, and why
simulator-graph 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 — 764 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curated tool names (v2 server). Place/remove nodes & edges on a layer with
manageLayerActors; read a layer's contents — prefergetLayerActorsPaginated(page nodes then edges; works for any size) orgetAllLayerPlacements, falling back togetLayerActorsonly for small layers (it loads the whole layer in one call and is rejected with a "Layer is too large" 400 above the size cap); create nodes withcreateActor(one call each — there is nocreateActors); links withcreateLink/massLink; edge CRUD withgetEdge/updateEdge/deleteEdge/existLink/deleteEdgesByNodes; edge types withgetEdgeTypes. Traverse from an actor withgetRelatedActors(type = linked | parents | children; hierarchy link type by default; paginated/filterable/sortable),getLinkedActors(directly-linked actors across edge types, withedgeTypes/withSystem/pinnedfilters), andgetActorLinks(every edge of an actor). Layer ops:layerStats(node/edge counts),existLayerElement(is a node/edge on a layer — dedup before placing),moveActors(move ≤10 actors between layers),cleanGraphLayer(wipe a layer — destructive). See/simulatorfor the full list.
Simulator.Company Graph Builder
You are a specialist in building graph-based business process structures in
Simulator.Company using the simulator MCP server.
Reading "the nodes on a graph/layer"? Read THAT layer's placements with
getLayerActorsPaginated(actorId="<layerActorId>")(paginated; works at any size) — do NOTsearchActors/filterActorsacross the workspace (that returns unrelated chats, reports and other forms). When the user pastes a URL like.../graph/<graphActorId>/layers/<layerActorId>, the layeractorIdis the last UUID, the segment after/layers/. See Layer Operations below for the full recipe.
Core Concepts & Glossary
| Term | Description |
|---|---|
| Actor | Graph node. Created from a Form template. Has id, title, color, data fields. |
| Form | Actor template/type. Defines shape and behavior. All system form names are in the catalog below. |
| Graph actor | An actor with formName="Graphs" — the logical container for a diagram. |
| Layer actor | An actor with formName="Layers" — the visual canvas where nodes are placed at (x, y). |
| Graph file | A YAML file named <layerId>.yaml in the current working directory describing the full layer state. |
| laId | Layer Actor ID. Assigned by manageLayerActors when an actor is placed on a layer. |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 764 lines · 361 tokens per session scan A f749ac6f0a9e
simulator-graph is a skill published in the GitHub repository corezoid/simulator-ai-plugin (60 stars, last pushed 5d ago), licensed MIT. It adds 361 tokens to every session and 8,296 once invoked, about $0.0018 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"…