agentmods.dev

optimize-plugin

optimize-plugin is a skill for Claude Code from FradSer/dotclaude. It costs 40 tokens per session (1,160 once invoked), scanned A, original, MIT.

A workflow for checking and improving a Claude Code plugin, which is a package of commands, agents, skills, or hooks for Claude Code. It first validates the plugin structure and then can apply fixes through a separate agent.

In plain words
What is it for?
Use it to validate a plugin's manifest, structure, front matter, tool usage, and token usage. It can also inspect whether command files should be changed into skills.
Why use it?
It helps find missing files, invalid component layouts, and other plugin problems before release. Separating checking from fixing makes the validation results easier to review.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions .claude-plugin; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the plugin-optimizer plugin — 2 skills, 1 agent shipped together

not rated 593repo 7d ago A scan 40 tokens original MIT

Good fit Use it to validate a plugin's manifest, structure, front matter, tool usage, and token usage. It can also inspect whether command files should be changed into skills.

Compare 6 skills from other repositories ↓
View source ↗ FradSer/dotclaude dotclaude.frad.me
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add FradSer/dotclaude
Claude Code
/plugin install plugin-optimizer

Made for: Claude Code.

Or install plugin-optimizer, the plugin that ships this one along with the rest of its 2 skills, 1 agent.

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 optimize-plugin

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/fradser/dotclaude/optimize-plugin"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/optimize-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00040 $0.01160
Opus 5.5 $0.00016 $0.00464
Sonnet 5.5 $0.00008 $0.00232
Haiku 4.5 $0.00004 $0.00116

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

Security

Grade A, and why

optimize-plugin 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 22d 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.

plugin-optimizer/skills/optimize-plugin/SKILL.md · 127 lines

How it starts

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

Plugin Optimization

Execute plugin validation and optimization workflow. Target: $ARGUMENTS

Background Knowledge

Load plugin-optimizer:plugin-best-practices skill using the Skill tool for component templates, tool invocation rules, and type classification.

Phase 1: Discovery & Validation

Goal: Validate structure and detect issues. Orchestrator MUST NOT apply fixes.

Actions:

  1. Resolve path with realpath and verify existence
  2. Validate .claude-plugin/plugin.json exists
  3. Find component directories: commands/, agents/, skills/, hooks/
  4. Validate components against ${CLAUDE_PLUGIN_ROOT}/examples/ templates
  5. Assess architecture: if commands/ exists with .md files, use AskUserQuestion tool to ask about migrating to skills structure
  6. Run validation: python3 ${CLAUDE_PLUGIN_ROOT}/scripts/validate-plugin.py "$TARGET"
    • Options: --check=structure,manifest,frontmatter,tools,tokens
    • JSON output: --json
    • Verbose: -v, --verbose
  7. Compile issues by severity (Critical, Warning, Info)

Phase 2: Agent-Based Optimization

Goal: Launch agent to apply ALL fixes. Orchestrator does NOT make fixes directly.

Condition: Always execute.

Actions:

  1. Launch plugin-optimizer:plugin-optimizer agent with the following prompt content:
    • Target plugin path (absolute path from Phase 1)
    • Validation console output (issues list from Phase 1)
    • Template validation results
    • User decisions (migration choice if applicable)
    • INSTRUCTION: Analyze the validation output to identify issues
  2. Agent autonomously applies fixes (MUST use AskUserQuestion tool before applying template fixes, presenting violations with specific examples and before/after comparison)
  3. Agent increments version in .claude-plugin/plugin.json after fixes:
    • Patch (x.y.Z+1): Bug fixes
    • Minor (x.Y+1.0): New components
    • Major (X+1.0.0): Breaking changes
  4. Wait for agent to complete

Path Reference Rules:

  • Same directory: Use relative paths (./reference.md)
  • Outside directory: Use ${CLAUDE_PLUGIN_ROOT} paths
  • Component templates: See ${CLAUDE_PLUGIN_ROOT}/examples/

Read the full file on GitHub · 127 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. 22d ago First seen · 127 lines · 40 tokens per session scan A 9be9e216ce82

Subscribe to this mod's changes

optimize-plugin is a skill published in the GitHub repository FradSer/dotclaude (593 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 1,160 once invoked, about $0.0002 per session on Opus 5.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-24.

Building agentsclaude
Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens