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 YunYouJun/craft-hub --skill craft-hub-plugin-creatorgit clone --depth 1 https://github.com/YunYouJun/craft-hubWrote 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/yunyoujun/craft-hub/craft-hub-plugin-creator)<a href="https://agentmods.dev/skills/yunyoujun/craft-hub/craft-hub-plugin-creator"><img src="https://agentmods.dev/badge/skills/yunyoujun/craft-hub/craft-hub-plugin-creator/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/yunyoujun/craft-hub/craft-hub-plugin-creator"><img src="https://agentmods.dev/badge/skills/yunyoujun/craft-hub/craft-hub-plugin-creator.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.00045 | $0.00497 |
| Opus 5.5 | $0.00018 | $0.00199 |
| Sonnet 5.5 | $0.00009 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
craft-hub-plugin-creator 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 — 22 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft Hub Marketplace Plugin creator
Use Craft Hub's CLI as the implementation and the repository runtime Schema as the contract. Read docs/guide/plugin-authoring.md before creating a plugin. Read docs/guide/plugin-marketplace.md when the request uses advanced contribution, permission, dependency, or Catalog fields.
Route the request
- Create: obtain an explicit scoped package name, display name, and license. Never infer identity, Publisher, or licensing from Git or npm state. Select any requested
commands,skills, andprojectTemplates, then callcraft-hub plugin:initwith--non-interactiveand the corresponding--with-*options. The target must be absent or empty. - Validate or diagnose: call
craft-hub plugin:validate <path>. Report every failing invariant. Modify the package only when the user asked to create, fix, or update it; validation requests remain read-only. - Test locally: validate first and resolve the plugin directory to an absolute path. Show that path and obtain explicit confirmation immediately before
craft-hub plugin:link. State the matchingplugin:unlink <package>recovery command. Refresh an existing confirmed link withplugin:refreshafter edits. - Pack: require an explicit Publisher, then call
craft-hub plugin:pack <path> --publisher <id>. Review the emitted tarball path, SHA-512 integrity, and Catalog Entry draft. Leave npm publication, Catalog modification, and Catalog signing to a separately authorized workflow.
Inside this repository, invoke the source CLI with pnpm --filter craft-hub exec tsx src/cli.ts <command>. For an installed package, invoke craft-hub <command>.
Completion
A created plugin is complete when plugin:validate succeeds and every requested contribution appears in its npm pack file list. A packed plugin is complete when both new artifacts exist in the selected output directory and the Catalog Entry integrity matches the actual tarball. Keep the generated placeholders visible to the user; they require domain-specific authoring before publication.
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 · 22 lines · 45 tokens per session scan A da42ff6b0270
craft-hub-plugin-creator is a skill published in the GitHub repository YunYouJun/craft-hub (1 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 497 once invoked, about $0.0002 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-09-07.
Other skills, from other repositories
posthog
Complete guide for the PostHog plugin — REST API access for querying analytics with HogQL, managing feature flags, inspecting events and persons, reading insights, experiments, cohorts, surveys, and more.
create-remotion-video
Create or edit video with Remotion. First-party clodex + Remotion skill. Contains full video-making process.
figma
Complete guide for the Figma plugin — REST API access, real-time selection monitoring via CDP, and the figma-app interactive UI. Read this IMMEDIATELY when the user asks to work with Figma.
github
Complete guide for the GitHub plugin — REST API access for repositories, issues, pull requests, actions, releases, and search using a GitHub Personal Access Token.
supabase
Complete guide for the Supabase plugin — Management API access for running SQL queries, listing projects, managing edge functions, secrets, migrations, and inspecting project health.
javascript-sandbox
Best practices for using the clodex built-in JavaScript sandbox for browser debugging, fetched-data processing, attachments, and mini-app orchestration within its bundled capability boundary.