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 zhebil/claude-code-plugins --skill configuregit clone --depth 1 https://github.com/zhebil/claude-code-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/zhebil/claude-code-plugins/configure)<a href="https://agentmods.dev/skills/zhebil/claude-code-plugins/configure"><img src="https://agentmods.dev/badge/skills/zhebil/claude-code-plugins/configure/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/zhebil/claude-code-plugins/configure"><img src="https://agentmods.dev/badge/skills/zhebil/claude-code-plugins/configure.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.00078 | $0.02751 |
| Opus 5.5 | $0.00031 | $0.01100 |
| Sonnet 5.5 | $0.00016 | $0.00550 |
| Haiku 4.5 | $0.00008 | $0.00275 |
Grade B, and why
configure scanned grade B 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `cat "${CLAUDE_PLUGIN_DATA:-$HOME/.claude}/config.json" 2>/dev/null || cat "$HOME/.claude/unfurl-context.json" 2>/dev/null || echo "(no config file - defaults apply)"` How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
unfurl-context: explain + configure
User-invoked only. Don't run as a side effect of unrelated work. If the user mentions Jira / GitHub / GitLab / Sentry without asking to configure unfurl-context, ignore this skill.
What this skill does
Explain to the user what unfurl-context is, gather the current state in one pass (parallel CLI + auth + config checks), present a concise summary of "what's on, what's off, what you can change", and then act on whatever the user actually wants. Don't walk through numbered steps. Don't ask the user permission between every check. Don't re-prompt for things you can detect.
The user already triggered the skill because they want information. Lead with the explanation and the current state, not with questions.
The flow
1. Explain the plugin (short)
Open with a single tight paragraph. Cover:
- What it does: when the user submits a prompt mentioning a GitHub PR/issue/repo/file, GitLab issue/MR/project/file, Jira ticket, or Sentry issue, the plugin runs before Claude reads the prompt and prepends a compact markdown summary of that reference fetched via local CLIs (
gh,glab,acliorjira,sentry). GitHub file URLs (/blob/,/raw/,raw.githubusercontent.com) and GitLab file URLs (/-/blob/,/-/raw/) embed the file contents, with optional line anchors for slicing. - Why it needs CLI auth: the plugin doesn't store credentials. It just runs the CLIs as the user, so the CLIs need to be logged in to GitHub / GitLab / Atlassian / Sentry on their own. There's nothing to "configure" auth-wise inside the plugin.
- Code blocks are skipped: refs inside backticks or fenced blocks are never enriched.
- Each ref is enriched once per session (dedup state in
$CLAUDE_PLUGIN_DATA/seen.json, preserved across/compact).
Keep this to roughly 4-6 lines. Don't reproduce the README.
2. Gather current state in ONE parallel batch
Without asking, run the install + auth + config checks at the same time. Use a single tool message with parallel Bash calls. Don't do them sequentially and don't pause to confirm.
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.
- today First seen · 135 lines · 78 tokens per session scan B 04dea2be2e62
configure is a skill published in the GitHub repository zhebil/claude-code-plugins (7 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 2,751 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-18.
Other skills, from other repositories
predictable-revenue
Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
team-topologies
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or…
structured-plan-mode
This skill should be used when planning and tracking complex feature implementations that require systematic task decomposition. Use this skill to break down large features into manageable, well-documented tasks with clear dependencies, action items, and success criteria. The skill provides a structured template and…
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
dev-kit-setup
First-use bootstrap for the dev kit. Detects the team's issue tracker, discovers what it can via MCP/CLI, asks only what cannot be discovered, and persists the result to .claude/dev-kit.json in the consuming repo. Use when that file is missing, when the user asks to set up or reconfigure the kit, or when issue-fetch…