Borrowing it
Nothing to install: this file belongs to devrelaicom/tome. 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/devrelaicom/tome/main/.claude/skills/convert-marketplace/SKILL.mdgit clone --depth 1 https://github.com/devrelaicom/tomeWrote 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/devrelaicom/tome/convert-marketplace)<a href="https://agentmods.dev/skills/devrelaicom/tome/convert-marketplace"><img src="https://agentmods.dev/badge/skills/devrelaicom/tome/convert-marketplace.svg" alt="Measured on agentmods" 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.00065 | $0.01855 |
| Opus 5 | $0.00032 | $0.00928 |
| Sonnet 5 | $0.00013 | $0.00371 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
convert-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 6d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convert a Claude Code marketplace to Tome
You are converting a Claude Code marketplace (a collection of plugins, each with
skills / commands / agents) into Tome's native format so the plugins work across
every harness Tome supports. Tome does the mechanical 80% — format translation,
harness-variable rewriting, manifest synthesis — through tome convert and
tome lint. Your job is the judgment 20%: the components Tome cannot represent,
the verification, and — above all — stopping to report and get the user's
explicit confirmation before you register anything in a workspace.
Work through the steps in order. Do not skip the report-and-confirm gate (Step 5) even if everything converted cleanly with nothing left over.
Step 1 — Inventory first, change nothing
Before touching anything, build a complete picture of what the source contains and what Tome can and cannot carry over.
- Run the conversion in dry-run mode and read the plan:
tome catalog convert <source> --dry-run --json<source>is the marketplace directory. (For a single plugin or skill rather than a whole marketplace, usetome plugin convert/tome skill convertinstead.) The JSON plan enumerates every plugin and entry that will convert, and — critically — every unsupported component Tome flagged (monitors, themes, LSP servers, output-styles, status-line scripts,bin/helpers, channels, customuserConfig, and so on). - Summarise for yourself: how many plugins, how many skills / commands / agents convert cleanly, and the full list of flagged unsupported components. This list is your Step 3 work queue — nothing leaves it without an explicit decision.
Do not run a non-dry-run convert yet.
Step 2 — Mechanical conversion
Now run the real conversion — it lands a fresh catalog directory on disk (the source is never modified) — and read what happened:
tome catalog convert <source> --output <parent-dir> --json
--output is the parent directory the new catalog lands under; the catalog itself
is created at <parent-dir>/<name>/ (call that produced directory <catalog> in
the steps below). --output defaults to the current directory if omitted.
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.
- 6d ago First seen · 179 lines · 65 tokens per session scan A f18b8c6cfdad
convert-marketplace is a skill published in the GitHub repository devrelaicom/tome (4 stars, last pushed 5d ago), licensed Apache-2.0. It adds 65 tokens to every session and 1,855 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…