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 agentmods add skills/martineserios/thebrana/pluginnpx skills add martineserios/thebrana --skill plugingit clone --depth 1 https://github.com/martineserios/thebranaWrote 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/martineserios/thebrana/plugin)<a href="https://agentmods.dev/skills/martineserios/thebrana/plugin"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/plugin.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 | $0.00031 | $0.01980 |
| Opus 5 | $0.00015 | $0.00990 |
| Sonnet 5 | $0.00006 | $0.00396 |
| Haiku 4.5 | $0.00003 | $0.00198 |
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 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.
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>/" How it starts
The opening of the file, as written. The whole thing — 270 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:
-
Validate format: must be
owner/repo(e.g.,martineserios/thebrana). -
Read
~/.claude/plugins/known_marketplaces.json. Create if missing:{} -
Check if marketplace already registered. If yes, ask user:
- question: "Marketplace already registered. Update it?"
- options: ["Yes — re-clone", "No — skip"]
-
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) -
Verify
.claude-plugin/marketplace.jsonexists in the cloned repo. If missing, abort with error. -
Read the marketplace manifest to confirm it's valid JSON with a
pluginsarray. -
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 } }
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 · 270 lines · 31 tokens per session scan C 09bf84425316
plugin is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 1,980 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
exec
Execute plan tasks sequentially using subagents. Use when user says 'exec', 'execute plan', 'run plan', or wants to implement a plan file task by task with isolated subagents.
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.
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…
ask-codex
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…
new
Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.
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…