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 skills add corezoid/corezoid-ai-plugin --skill corezoid-gitcallgit 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-gitcall)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/corezoid-gitcall"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-gitcall/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-gitcall"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-gitcall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 223 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00154 | $0.03305 |
| Opus 5.5 | $0.00062 | $0.01322 |
| Sonnet 5.5 | $0.00031 | $0.00661 |
| Haiku 4.5 | $0.00015 | $0.00331 |
Grade A, and why
corezoid-gitcall 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 1mo 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corezoid Git Call
A Git Call node runs your code (9 built-in languages, or a custom Docker image)
in an isolated container as one step of a process. Each task is delivered to a
handle function over JSON-RPC 2.0; the value you return becomes the payload of
the next node.
1. When to use it — the selection rule
Git Call is one of the most constrained nodes on the platform. Use it only
when a step needs a capability that native nodes and a Code (api_code) node
cannot provide — parsing a file, an external library, cryptography, or a custom
runtime — and the work finishes comfortably within the observed runtime
budget. For everything else use the native alternative. "One code block is
easier to write" is not one of those capabilities.
Runtime and resource constraints
- Observed execution deadline: hosted sandbox measurements terminated the
handler at approximately 60 s, wall-clock from the moment the task entered the
node. Keep handler work comfortably below 50 s rather than relying on the exact
cutoff, which is an observed platform behavior rather than a portable contract.
On overrun the task was killed and routed to the error path
(
__conveyor_git_call_return_type_tag__ = git_call_executing_error, descriptionusercode: timeout). In those measurements, inline cold and warm runs ended at the same point; custom images may have different startup overhead. - Default resource allocation: 50 MB RAM and 0.1 CPU from a pool shared by Git Call nodes. These are defaults, not immutable hard limits: a super-admin can change the allocation. Shared capacity can still cause contention under concurrency; one live concurrent probe observed a starved task.
- No persistent local storage: runtime-local files, including writable
/tmp, are ephemeral and must not be used as state between runs. - Build-time network dependency: Git-repo mode and dependency installation need network access. Runtime network access is required only when the handler itself calls an external service.
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.
- 1mo ago First seen · 270 lines · 154 tokens per session scan A d76d11705fad
corezoid-gitcall is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (74 stars, last pushed yesterday), licensed MIT. It adds 154 tokens to every session and 3,305 once invoked, about $0.0006 per session on Opus 5.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
superloopy-backend
Use only after explicit Codex $superloopy:superloopy-backend or Claude Code /superloopy:superloopy-backend invocation, a backend task beginning with leading loopy or 루피, or an active Superloopy loop routes backend work here. Relevant work includes backend application boundaries, APIs, persistence, migrations…
amocrm-api-control
A guide for securely connecting to amoCRM, a customer-relationship system, through its API. It covers OAuth sign-in, account structure, and checking leads by source, time, status, owner, and external link.
architecture
Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.
bitrix24-bi-reports
A procedure for building and checking business reports in Bitrix24's BI Constructor, which uses Apache Superset to query and display data. It connects advertising costs with leads, deals, calls, and revenue, while checking figures against CRM data.
bitrix24-crm-api
A guarded connection to Bitrix24, a customer-management system, through its REST interface. It can read leads, deals, sales stages, sources, tracking data, calls, and stage history, while restricting changes unless the owner approves a detailed plan.
govard-laravel
This skill should be used when the user asks to "run migrations", "run artisan commands", "clear Laravel cache", "config:cache", "run queue operations", "schedule:run", "tinker into app", "artisan tinker", "run Laravel Pint", "lint Laravel project", "audit Laravel", "govard audit", "npm dev/prod", "deploy Laravel", or…