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/corezoid-ai-plugin/corezoid-createnpx skills add corezoid/corezoid-ai-plugin --skill corezoid-creategit clone --depth 1 https://github.com/corezoid/corezoid-ai-pluginWrote 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-create)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/corezoid-create"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-create.svg" alt="Measured on agentmods" 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.00089 | $0.03978 |
| Opus 5 | $0.00044 | $0.01989 |
| Sonnet 5 | $0.00018 | $0.00796 |
| Haiku 4.5 | $0.00009 | $0.00398 |
Grade A, and why
corezoid-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 6d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a New Corezoid Process
You are a specialist in creating Corezoid BPM processes using the corezoid MCP server.
Step 1: Gather Requirements
Ask the user for the following before proceeding:
- Process purpose — what should it do?
- Input parameters — what data does it receive?
- Expected output — what should it return on success?
- Process type — API connector (calls an external HTTP API) or business logic (orchestrates other Corezoid processes)?
For API connector, also require:
METHOD— HTTP method (GET, POST, PUT, etc.)URL— endpoint URL (use a Corezoid variable, never hardcode)AUTH— authentication method and token variable name
⚠️ If the target API is the Corezoid public API (
/api/2/json/), stop here and use/corezoid-api-connectorinstead — it follows a different pattern (api_secret_outer,opsarray, no Code Node for signing).
If any required information is missing, ask the user before proceeding.
Step 2: Create the Empty Process
Call MCP tool create-process with:
folder_path: Relative path to the folder directory. Omit to use the current directory.process_name: the process name
This creates an empty process in Corezoid and saves the file as <ID>_<Name>.conv.json inside folder_path. The returned file path is PROCESS_PATH — all subsequent steps use it.
⚠️ Always verify
folder_pathpoints to the intended target folder. Omitting it places the process in the project root, which may not be the correct location.
⚠️ After
create-process, Corezoid may create default template nodes (Start, a placeholder process node, Final) even withcreate_mode: without_nodes. Before generating the full JSON, check the currentscheme.nodesarray in the created file. If a Start node already exists, do not add another — doing so will cause a validation error.
If the process type is business logic and it needs to call existing processes, find their conv_id values by browsing the already-exported .conv.json files in the project folder.
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.
- 6d ago First seen · 251 lines · 89 tokens per session scan A edf0bd77638b
corezoid-create is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (73 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 3,978 once invoked, about $0.0004 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
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
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.