Borrowing it
Nothing to install: this file belongs to musingfox/cc-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/musingfox/cc-plugins/main/.claude/skills/marketplace/SKILL.mdgit clone --depth 1 https://github.com/musingfox/cc-pluginsWrote 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/musingfox/cc-plugins/marketplace)<a href="https://agentmods.dev/skills/musingfox/cc-plugins/marketplace"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/marketplace/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/musingfox/cc-plugins/marketplace"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/marketplace.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.00097 | $0.01256 |
| Opus 5 | $0.00048 | $0.00628 |
| Sonnet 5 | $0.00019 | $0.00251 |
| Haiku 4.5 | $0.00010 | $0.00126 |
Grade A, and why
marketplace 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-plugins marketplace maintenance
This repo is a marketplace of independent plugins. Four things must agree at all times; any one of them drifting is a defect, not a cosmetic issue.
| Artifact | Where | What breaks if it drifts |
|---|---|---|
| Plugin manifest | <plugin>/.claude-plugin/plugin.json |
Plugin does not load |
| Marketplace entry | .claude-plugin/marketplace.json |
Plugin is not installable |
| README section + structure tree | README.md |
Users cannot find or install it |
version in plugin.json |
same manifest | No bump → no cache refresh; users keep running the old copy |
The plugin / marketplace spec itself follows the official Claude Code documentation.
Consult the docs (ctx7 docs /websites/code_claude) rather than inferring conventions
from neighbouring plugins — the neighbours may be stale.
Writing the components
The four artifacts above are bookkeeping; what goes inside a skill is a separate
craft. Read WRITING.md whenever you write or revise a skill's
description or body, or edit CLAUDE.md. It carries the judgment: how a description's
wording decides whether the skill fires, when a skill should be user-invoked instead
(disable-model-invocation: true) and pay no context load at all, what belongs in a
sibling file rather than in SKILL.md, and which sentences are no-ops to delete.
For the mechanics — frontmatter fields, directory layout, eval tooling — use
plugin-dev:skill-development and skill-creator instead.
Adding a plugin
- Create
<plugin>/.claude-plugin/plugin.json. Copy the field set from an existing manifest (name,description,version,author,keywords,homepage,license);homepagepoints at.../tree/main/<plugin>. Start at0.1.0. - Add the components —
skills/,commands/,agents/,scripts/. Auto-discovery finds them by directory; no manifest wiring needed. - Append an entry to
.claude-plugin/marketplace.jsonplugins[]:{"name", "source": "./<plugin>", "description"}. Keepdescriptionin sync with the manifest's — they are read in different places and users compare them. - Add a
### <Plugin>section to README.md under Available Plugins (what each component does, plus the/plugin install <name>block) and a row to the structure tree under Plugin Development.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 102 lines · 97 tokens per session scan A 3a62cb975bd6
marketplace is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 1,256 once invoked, about $0.0005 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-09-09.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.