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-create)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/corezoid-state-diagram-create"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-state-diagram-create/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-create"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-state-diagram-create.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.00118 | $0.02997 |
| Opus 5 | $0.00059 | $0.01499 |
| Sonnet 5 | $0.00024 | $0.00599 |
| Haiku 4.5 | $0.00012 | $0.00300 |
Grade A, and why
corezoid-state-diagram-create 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 12d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a New Corezoid State Diagram
You are a specialist in creating Corezoid state diagrams (conv_type: "state") using the corezoid MCP server.
A state diagram is a long-lived data store: each task is one entity's state, referenced by a stable ref. Other processes read, create, and modify these state tasks. The state diagram itself only contains states (parked tasks), transitions between them, and a tiny subset of helper nodes.
Before you start, make sure you understand:
- A state diagram has
conv_type: "state"at the root (not"process"). - Only 10 node types are allowed: Start, Condition, Code, Set Parameters, Copy Task, Modify Task, Set State (= a state node), Delay, Queue, End: Success, End: Error.
- API Call, Call a Process, Reply to Process, DB Call, Git Call, Sum, API Form are forbidden inside a state diagram — they belong in the driver process.
Read ${CLAUDE_PLUGIN_ROOT}/docs/state-diagrams/state-diagram-overview.md if you need a refresher on the model.
Step 1: Gather Requirements
Ask the user for the following before proceeding:
- What entity is being tracked? (user, order, device, subscription, account, …)
- What is the
ref? — the stable identifier (e.g.userId,orderId). This is the lookup key every reader and writer will use. - List the states. A name and a one-line description for each (e.g.
Pending,Active,Suspended,Closed). - List the transitions. For every state, what data change causes it to move to which other state? (e.g.
Active → Suspended when status == "suspended"). - Initial state. Which state does a newly created task enter first?
- Terminal states. Which states are "End: Success" / "End: Error", if any?
- Side effects on entry / exit (optional). Should entering a state trigger a notification, stamp a timestamp, etc.? (These are Copy Task / Modify Task nodes between states.)
If any of the above is missing, ask the user before continuing.
Step 2: Create the Empty State Diagram
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.
- 12d ago First seen · 228 lines · 118 tokens per session scan A 1bd22955f4df
corezoid-state-diagram-create is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (72 stars, last pushed today), licensed MIT. It adds 118 tokens to every session and 2,997 once invoked, about $0.0006 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
frappe-fullstack
End-to-end Frappe and ERPNext implementation guidance spanning backend Python, backend JavaScript surfaces, Vue or React frontends, customizations, and bench-aware delivery. Use when the task crosses multiple Frappe layers.
frappe-customization
Frappe customization-surface guidance covering Custom Field, Property Setter, Client Script, Server Script, Workspace, Web Page, Page, Print Format, Report, Dashboard, Workflow, Role, Notification, Webhook, and related builder/admin DocTypes. Use when choosing or changing Frappe customization layers.
frappe-backend
Frappe backend guidance for Python and backend-adjacent JavaScript surfaces such as client interaction patterns, hooks, APIs, patches, scheduler logic, reports, and server-side review. Use when implementing or reviewing Frappe backend behavior.
frappe-search
Frappe-specific search and discovery guidance for finding benches, apps, remotes, sites, ports, hooks, DocTypes, builder DocTypes, and frontend surfaces quickly. Use when the task starts with locating or classifying Frappe context.
sdlc-spec-slice-writer
Use to write focused implementation SPEC slices for UI, API, data, admin, permissions, directory, observability, or release.
dev-api-contract-review
Use to design or review API contracts, auth, pagination, versioning, errors, compatibility, and OpenAPI/GraphQL shape.