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 tamnguyendinh/Anvien --skill plugin-marketplacegit clone --depth 1 https://github.com/tamnguyendinh/AnvienWrote 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/tamnguyendinh/anvien/plugin-marketplace)<a href="https://agentmods.dev/skills/tamnguyendinh/anvien/plugin-marketplace"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/plugin-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/tamnguyendinh/anvien/plugin-marketplace"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/plugin-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.00035 | $0.00519 |
| Opus 5 | $0.00017 | $0.00260 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
plugin-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 9d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Marketplace
Operational guide for building and maintaining Claude Code plugin marketplaces.
Activation Boundary
Use this skill only when the task involves plugin marketplace distribution:
- Creating or editing
.claude-plugin/marketplace.json - Publishing a marketplace to GitHub, GitLab, Bitbucket, a git URL, or a local path
- Defining plugin source entries for marketplace installation
- Reviewing team marketplace allowlists or managed marketplace restrictions
- Debugging marketplace validation, install, update, or authentication failures
Do not use this skill for ordinary SKILL.md creation or skill quality review unless the user is also asking to distribute the skill through a plugin marketplace.
Core Rule
Inspect the target repository or marketplace folder before giving instructions.
Confirm:
- Existing
.claude-plugin/marketplace.json - Existing plugin folders and
.claude-plugin/plugin.jsonmanifests - Whether sources are relative paths, GitHub repositories, git URLs, npm packages, or local paths
- Whether the marketplace is public, private, team-managed, or local-only
- Which command surface the user is using: Claude Code slash commands, CLI validation, or repository configuration
Do not invent marketplace fields. Follow the existing manifest shape or the schema reference.
Workflow
- Determine whether the user needs a marketplace catalog, a plugin entry, hosting guidance, or troubleshooting.
- Inspect existing marketplace files before editing.
- Use the schema reference for field names and required/optional structure.
- Use the source-types reference before choosing where plugin code is loaded from.
- Use hosting guidance when the task involves sharing, private repositories, or team policy.
- Use troubleshooting guidance only for observed validation, install, update, path, or auth failures.
Reference Navigation
- Marketplace setup:
references/plugin-marketplace-setup-overview.md - Marketplace JSON schema:
references/plugin-marketplace-json-schema.md - Plugin source types:
references/plugin-marketplace-source-types.md - Hosting and distribution:
references/plugin-marketplace-hosting-distribution.md - Errors and fixes:
references/plugin-marketplace-errors-and-fixes.md
What ships with it
5 files 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.
- 9d ago First seen · 58 lines · 35 tokens per session scan A 15e4c32276db
plugin-marketplace is a skill published in the GitHub repository tamnguyendinh/Anvien (9 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 519 once invoked, about $0.0002 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-03.
Other skills, from other repositories
kin-retrieval
Read a codebase through Kin's semantic graph instead of grep and whole-file reads. Use when finding where something lives, what a symbol does, who calls it, or which code implements a described behavior, and when a repo has been admitted to Kin (a .kin/ directory exists).
blast-radius-review
Review a change by its blast radius, using Kin's graph to find what downstream code the change can reach. Use when reviewing a diff or pull request, deciding whether an edit is safe, or answering "what else breaks if I change this" in a repository admitted to Kin.
booboo-deploy
Stand up a Booboo brain end to end — scaffold the project, write booboo.config.yaml against a real Postgres/Supabase or JSON source, build the snapshot, then wire the REST API, the MCP server, the 3D viewer and the panel. Use when someone wants a brain built for the first time, wants to point Booboo at their own…
booboo-troubleshoot
Diagnose a Booboo brain that is not working — an empty or tiny graph, a flat starburst view, missing MCP tools, a client that cannot find the snapshot, climbing orphan counts, or a build that exits clean but produces nothing. Use when a booboo build, serve, mcp, view, panel or vault command misbehaves.
booboo
Build, query, deploy and debug a Booboo brain — one graph fusing structure, knowledge, memory, agents and automations, queryable by REST or MCP and viewable in 3D. Use when the user mentions Booboo, booboo.config.yaml, brain.json, org.booboo.json, an organigram of agents, "boot my agent from the org", a 3D system…
booboo-adapter
Feed data into a Booboo brain that the built-in postgres and json adapters do not cover — write a small config-driven adapter against the spec instead of forking the builder. Use when a source is Neo4j, an API, a CSV export, a proprietary store, or any shape the standard config cannot express.