plugin

plugin is a skill for Claude Code from martineserios/thebrana. It costs 31 tokens per session (2,640 once invoked), scanned C, original, MIT.

A command for managing Claude Code plugins from GitHub marketplaces.

In plain words
What is it for?
It is for adding marketplaces, installing, updating, listing, removing, and synchronising Claude Code plugins.
Why use it?
It provides one workflow for registering marketplaces and keeping installed plugins up to date.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; mentions .claude-plugin.

Part of the brana plugin — 53 skills, 4 commands, 14 agents shipped together

Good fit It is for adding marketplaces, installing, updating, listing, removing, and synchronising Claude Code plugins.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/martineserios/thebrana/plugin
Install

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.

Any agent
npx skills add martineserios/thebrana --skill plugin
Clone the repo
git clone --depth 1 https://github.com/martineserios/thebrana

Made for: Claude Code.

Or install brana, the plugin that ships this one along with the rest of its 53 skills, 4 commands, 14 agents.

Wrote 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.

agentmods badge for plugin

README.md
[![agentmods](https://agentmods.dev/badge/skills/martineserios/thebrana/plugin/github.svg)](https://agentmods.dev/skills/martineserios/thebrana/plugin)
Your own site
<a href="https://agentmods.dev/skills/martineserios/thebrana/plugin"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/plugin/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.

agentmods 80×15 button for plugin

Your own site · 80×15
<a href="https://agentmods.dev/skills/martineserios/thebrana/plugin"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,640 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.02640
Opus 5.5 $0.00012 $0.01056
Sonnet 5.5 $0.00006 $0.00528
Haiku 4.5 $0.00003 $0.00264

Measured 9d ago against content hash 109b1134fb52, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

plugin scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$HOME/.claude/plugins/cache/*/<name>/"
system/skills/plugin/SKILL.md · 299 lines

How it starts

The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plugin

Manage Claude Code plugins from GitHub marketplaces. Install, update, remove, and list plugins — filling the gap until CC ships native /plugin commands.

Usage

/brana:plugin add <owner/repo>        — register a GitHub marketplace
/brana:plugin install <name>          — install a plugin from known marketplaces
/brana:plugin list                    — show installed + available plugins
/brana:plugin remove <name>           — uninstall a plugin
/brana:plugin update [name]           — update all or a specific plugin
/brana:plugin sync                    — sync dev plugin cache (--plugin-dir users)

File Locations

File Purpose
~/.claude/plugins/known_marketplaces.json Registered marketplace repos
~/.claude/plugins/installed_plugins.json Installed plugin registry (version 2)
~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/ Cached plugin files
~/.claude/plugins/marketplaces/<marketplace>/ Cloned marketplace repos

Subcommands

add <owner/repo>

Register a GitHub repo as a plugin marketplace.

Steps:

  1. Validate format: must be owner/repo (e.g., martineserios/thebrana).

  2. Read ~/.claude/plugins/known_marketplaces.json. Create if missing:

    {}
    
  3. Check if marketplace already registered. If yes, ask user:

    • question: "Marketplace already registered. Update it?"
    • options: ["Yes — re-clone", "No — skip"]
  4. Clone/update the marketplace repo:

    git clone --depth 1 "https://github.com/<owner>/<repo>.git" \
        "$HOME/.claude/plugins/marketplaces/<repo-name>/" 2>/dev/null \
    || (cd "$HOME/.claude/plugins/marketplaces/<repo-name>/" && git pull --ff-only)
    
  5. Verify .claude-plugin/marketplace.json exists in the cloned repo. If missing, abort with error.

  6. Read the marketplace manifest to confirm it's valid JSON with a plugins array.

  7. Add entry to known_marketplaces.json:

    {
      "<repo-name>": {
        "source": {
          "source": "github",
          "repo": "<owner>/<repo>"
        },
        "installLocation": "/home/<user>/.claude/plugins/marketplaces/<repo-name>",
        "lastUpdated": "<ISO timestamp>",
        "autoUpdate": true
      }
    }
    

Read the full file on GitHub · 299 lines

Changes

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.

  1. 9d ago Changed · +29 lines 109b1134fb52
  2. 1mo ago First seen · 270 lines · 31 tokens per session scan C 09bf84425316

Subscribe to this mod's changes

plugin is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 2,640 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

pr

Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.

umputun/cc-thingz · 51 tokens

backlog

Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…

umputun/cc-thingz · 96 tokens

clarify

This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration…

umputun/cc-thingz · 91 tokens

writing-style

Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.

umputun/cc-thingz · 52 tokens

root-cause-investigator

Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.

umputun/cc-thingz · 53 tokens

last-tag

Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.

umputun/cc-thingz · 50 tokens