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 releasegit 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/release)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/release"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/release/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/release"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Prompt Injection · line 3 Subtle instructions detected that may alter agent decision-making or introduce hidden biases.Fix: Review content for implicit steering or bias. Ensure instructions are explicit and align with the skill's stated purpose.
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.00184 | $0.02578 |
| Opus 5.5 | $0.00074 | $0.01031 |
| Sonnet 5.5 | $0.00037 | $0.00516 |
| Haiku 4.5 | $0.00018 | $0.00258 |
Grade A, and why
release 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 24d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release skill
This skill prepares a new tagged release of corezoid-ai-plugin. It runs through six phases in order. Do not skip phases, and do not collapse them — the user expects to see and approve each one before the next begins.
Why a dedicated skill
A release of this plugin touches six separate manifest files (Claude, Codex, Kiro plugin manifests; two marketplace manifests; and POWER.md frontmatter) plus the changelog. Forgetting any one of them ships a broken or inconsistent release: marketplace listings disagree about the version, Codex/Kiro install the wrong build, or POWER.md — which is attached to the GitHub Release artifact set — advertises a stale version. The single source of release truth for this repo is RELEASE_CHECKLIST.md — this skill executes that checklist programmatically so nothing is missed.
The six phases
Phase 1 — Inspect what changed since the last tag
Goal: understand and summarise everything that has landed since the previous release.
Run, in parallel:
git fetch --tags --quiet
git describe --tags --abbrev=0 # the last released tag, e.g. v2.3.9
git log <last-tag>..HEAD --pretty=format:'%h %s' # commit subjects since that tag
git diff --stat <last-tag>..HEAD # files touched, magnitude of change
git status --short # uncommitted work that may need to ship in this release
Then read the actual diff for any commit subjects that are vague or for any non-trivial file changes — commit subjects alone often understate what shipped. Pay particular attention to:
- New skills under
plugins/corezoid/skills/(added directories). - MCP server changes in
plugins/corezoid/mcp-server/(new tools, schema changes, breaking behaviour). - Docs changes in
plugins/corezoid/docs/and root-level docs (README.md,SECURITY.md,CLAUDE.md). - CI / workflow changes in
.github/.
If git status shows uncommitted changes, ask the user whether those should be part of this release or stay out of it. Don't assume — pending edits are sometimes the whole point of the release and sometimes unrelated work.
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.
- 24d ago Changed · +184 tokens per session 97b03c120c23
- 1mo ago First seen · 191 lines · 0 tokens per session scan A a52bf7fa47af
release is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (74 stars, last pushed yesterday), licensed MIT. It adds 184 tokens to every session and 2,578 once invoked, about $0.0007 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
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
changelog
Record shipped work in the monthly changelog (append-only). Use when something ships or when asked "what changed", "add to changelog", "release notes", or "what shipped this month".
release-support
A release and upgrade support tool for 1C configurations, which are the structured applications built on the 1C platform. It covers checks around delivered updates, extensions, data migrations, and compatibility.
unica-release
A release workflow for publishing Unica to a public marketplace, checking its version, and continuing an unfinished release.
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.