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 marketplace-publish-validationgit 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/marketplace-publish-validation)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/marketplace-publish-validation"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/marketplace-publish-validation/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/marketplace-publish-validation"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/marketplace-publish-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00160 | $0.03572 |
| Opus 5 | $0.00080 | $0.01786 |
| Sonnet 5 | $0.00032 | $0.00714 |
| Haiku 4.5 | $0.00016 | $0.00357 |
Grade A, and why
marketplace-publish-validation 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 11d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketplace Publish Validation
You are a specialist in validating Corezoid projects for marketplace publication. Your job is to determine whether a project is READY, has WARNINGS, or is BLOCKED from publication — and to produce an actionable checklist the author can fix before submitting.
This is a standalone skill — it does not depend on any other skill. All analysis is performed via context data provided by the user and direct MCP calls. No external skill invocation is required.
Report language: Match the language of the user's request (default EN).
Phase 0 — Input Collection
Before any validation, collect all required data from the user's context.
Step 0.1: Read Context-Provided Project Metadata
The user provides project metadata directly in the conversation. Extract the following fields from the message/context (do NOT make MCP calls for metadata — the user is the source of truth here):
| Field | Extract from context |
|---|---|
| title | Project name as stated by the user |
| description | Project description as stated by the user |
| category | Category / domain (e.g. "fintech", "CRM", "logistics") |
| version | Version string if provided (e.g. "1.0.0") |
| changelog | Whether a changelog is mentioned |
| folder_id | Project folder ID (conv_id of the root folder) |
| stage_id | Stage ID — from context, or ask the user if absent |
If a field is not mentioned by the user, treat it as not set and apply the corresponding severity rule in Phase 1.
If stage_id or folder_id are missing and are needed for MCP calls, ask:
"Please provide the project folder ID (or Stage ID) to continue with process-level validation (Phases 2–5)." Phase 1 (metadata) can run immediately without them.
Step 0.2: Load Process Inventory
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.
- 11d ago First seen · 379 lines · 160 tokens per session scan A 6ddb6f76451a
marketplace-publish-validation is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (72 stars, last pushed 6d ago), licensed MIT. It adds 160 tokens to every session and 3,572 once invoked, about $0.0008 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-payments
Frappe Payments and ERPNext payment workflow guidance for payment gateways, payment requests, subscriptions, invoices, reconciliation, webhooks, and secure checkout flows. Use when work touches payments in Frappe or ERPNext.
stop-that-shit
Complete requested work while preventing speculative defenses and scope creep. Use when considering extra hardening, reviewing possible overengineering, resolving repeated verification loops, following explicit task boundaries, or when the user invokes Stop That Shit. Ordinary use of validation, retries, or…
shopify-apps
Shopify app development - Remix, Admin API, checkout extensions.
klaviyo
Klaviyo email/SMS marketing - profiles, events, flows, segmentation.
web-payments
Stripe Checkout, subscriptions, webhooks, customer portal.
woocommerce
WooCommerce REST API - products, orders, customers, webhooks.