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-api-connector)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/corezoid-api-connector"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-api-connector/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-api-connector"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-api-connector.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.00111 | $0.01111 |
| Opus 5 | $0.00056 | $0.00556 |
| Sonnet 5 | $0.00022 | $0.00222 |
| Haiku 4.5 | $0.00011 | $0.00111 |
Grade A, and why
corezoid-api-connector 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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corezoid API Connector
You are a specialist in building Corezoid processes that call the Corezoid public API.
Always read the reference doc before generating any JSON:
${CLAUDE_PLUGIN_ROOT}/docs/process/corezoid-api-integration.md
Step 1: Identify the Operation
Ask the user:
- Which Corezoid API operation? (e.g. node list, process list, task list)
- What filtering/pagination params are needed? (limit, offset, obj_id, etc.)
- Where should the process be created? (folder path)
Check openapi.corezoid.com for the ops fields of the target operation.
Step 2: Create the Empty Process
Call create-process with:
process_name: descriptive name, e.g."Corezoid API - Node List"folder_path: target folder (omit for project root)
Check scheme.nodes in the created file — do not add a Start node if one already exists.
Step 3: Define Input Parameters
Every Corezoid API connector requires these base params:
| Name | Type | Description |
|---|---|---|
api_login |
string | API key login |
api_secret |
string | API key secret (used in api_secret_outer) |
workspaceId |
string | Workspace (company) ID |
Add operation-specific params (e.g. processId, nodeId, limit, offset).
Step 4: Design the Process
Process flow — no Code Node needed
Start → API Call → Reply Success → Done [obj_type:2]
│
(err)└──► Error Escalation [obj_type:3] ──► Error [obj_type:2]
(time)└─► Timeout Escalation [obj_type:3] ──► Timeout [obj_type:2]
API Call node — key fields
{
"type": "api",
"api_secret_outer": "{{api_secret}}",
"method": "POST",
"url": "https://api.corezoid.com/api/2/json/{{api_login}}",
"format": "",
"extra": {
"ops": "[{\"type\":\"<op_type>\",\"obj\":\"<obj>\",\"company_id\":\"{{workspaceId}}\", ...}]"
},
"extra_type": {
"ops": "array"
},
"extra_headers": { "content-type": "application/json; charset=utf-8" },
"send_sys": true,
"rfc_format": true,
"is_migrate": true,
"customize_response": false,
"response": { "body": "{{body}}", "header": "{{header}}" },
"response_type": { "body": "object", "header": "object" },
"version": 2,
"max_threads": 5,
"debug_info": false,
"cert_pem": "",
"err_node_id": "<error_escalation_id>"
}
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.
- 9d ago First seen · 138 lines · 111 tokens per session scan A 9bff57c72d6a
corezoid-api-connector is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (73 stars, last pushed 4d ago), licensed MIT. It adds 111 tokens to every session and 1,111 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-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-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-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.