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/corezoid-ai-plugin/plugin install corezoidWrote 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/corezoid-ai-plugin/corezoid-state-diagram-edit)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/corezoid-state-diagram-edit"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-state-diagram-edit/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/corezoid-ai-plugin/corezoid-state-diagram-edit"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-state-diagram-edit.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.00131 | $0.02415 |
| Opus 5 | $0.00066 | $0.01208 |
| Sonnet 5 | $0.00026 | $0.00483 |
| Haiku 4.5 | $0.00013 | $0.00242 |
Grade A, and why
corezoid-state-diagram-edit 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 11d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit an Existing Corezoid State Diagram
You are a specialist in modifying Corezoid state diagrams (conv_type: "state") using the corezoid MCP server.
A state diagram is a long-lived data store; modifying it means changing the set of states, the data conditions that drive transitions between them, or the side effects performed on transition. The driver processes that read / write the diagram are usually edited separately via /corezoid-edit.
Read ${CLAUDE_PLUGIN_ROOT}/docs/state-diagrams/state-diagram-overview.md for a refresher on the model before editing.
Identify the State Diagram (MANDATORY FIRST STEP)
Before doing anything else, resolve PROCESS_PATH:
- Check whether the user already provided an identifier — a file path, state diagram name, or numeric id — in the current message or conversation history.
- If no identifier is provided, ask:
"Please specify the state diagram — a file path (e.g.
1863140_User_Status.conv.json), a name, or a state diagram id." Do not call any MCP tools until the user provides one. - If the user gives a name or id, search the local working directory for the matching
.conv.jsonusingfind/grep. - Open the file and confirm
"conv_type": "state"at the root. Ifconv_typeis"process", this is a regular process — hand off to/corezoid-editinstead. - Once
PROCESS_PATHis confirmed, analyze the file before changing anything.
Step 1: Analyze the State Diagram
Read the file and map out:
- The list of state nodes (every node with
obj_type: 0whose first logic isapi_callback). Note each state'sid,title, and outboundgo_if_consttransitions. - The Start node and which state it routes to (the initial state).
- Any helper nodes between states (Set Parameters, Code, Modify Task, Copy Task, Delay, Queue).
- Terminal nodes (
obj_type: 2).
🔍 If you see
obj_type: 3state nodes, you are looking at the legacy state-node format. The current Corezoid format usesobj_type: 0withapi_callbackas the first logic. Convert old nodes to the new format only if the user explicitly asks — otherwise leave them as-is and edit in place.
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.
- 11d ago First seen · 174 lines · 131 tokens per session scan A c39a4de7986d
corezoid-state-diagram-edit is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (73 stars, last pushed 6d ago), licensed MIT. It adds 131 tokens to every session and 2,415 once invoked, about $0.0007 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
stop-that-shit
Complete requested work while preventing speculative defenses and scope creep. Use when considering extra hardening, reviewing possible overengineering, resolving repeated verification loops, following explicit task boundaries, or when the user invokes Stop That Shit. Ordinary use of validation, retries, or…
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.
superloopy-loop
Use Superloopy's lightweight strict-evidence loop for Codex tasks that need durable progress, criteria, and artifact-backed completion.
superloopy-clone
Use when the user asks for Superloopy clone or asks to clone, rebuild, reverse-engineer, replicate, or copy a website or page into a Superloopy-governed implementation. Triggers on "loopy clone", target URLs plus requests such as "clone this site", "rebuild this page", "make a copy of this website", "pixel-perfect…
superloopy-doctor
Use when diagnosing Superloopy doctor, install, wrapper, plugin cache, hook bootstrap, bundled agents, marketplace, Codex, Claude Code, stale-version, evidence-floor, or host-wiring health problems.
inspect-codex-trajectory
Inspect or show a local Codex task trajectory, including turns, approximate model steps, assistant messages, reasoning summaries, tool calls, failures, compaction, token usage, and timing. Use when the user asks for a trajectory, execution trace, task timeline, slow-tool analysis, visual event ledger, or live…