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.
/plugin marketplace add huzaifa525/claude-code-optimizernpx agentmods add plugins/huzaifa525/claude-code-optimizer/marketplacegit clone --depth 1 https://github.com/huzaifa525/claude-code-optimizerGrade A, and why
claude-code-optimizer 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 2d 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.
What it actually says
{
"title": "Claude Code Optimizer",
"tagline": "Cut token costs 50-70% with smart skills, hooks, and rules",
"categories": [
"productivity",
"optimization",
"developer-tools",
"token-management"
],
"features": [
"25+ specialized skills for every workflow",
"13 automation hooks (protection, formatting, memory)",
"6 path-scoped rules (zero cost when inactive)",
"Auto-setup with stack detection",
"Persistent session memory across restarts",
"Subagent-driven development with two-stage review",
"Optimization modes (aggressive/balanced/thorough)",
"Git worktree isolation for safe development"
],
"screenshots": [],
"keywords": [
"token-optimization",
"skills",
"hooks",
"rules",
"productivity",
"cost-reduction",
"developer-tools",
"workflow-automation"
]
}
What ships with it
1 file beside marketplace.json 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.
- 2d ago First seen · 32 lines scan A bea9d3530590
claude-code-optimizer is a plugin published in the GitHub repository huzaifa525/claude-code-optimizer (9 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-08-31.
Other plugins, from other repositories
claude-hangar
Production-grade Claude Code environment with 42 skills, 22 agents, 31 hooks, and 9 framework stacks — optimized for Claude Code v2.1.116.
claude-hangar-dev
Development marketplace for Claude Hangar plugin.
skill-olympus
Plugin marketplace listing 1 plugin: skill-olympus.
skill-olympus
Twelve Greek gods. One command. A working SaaS. 100 public skill sources with a lightweight entrypoint-only registry, 42 optional agent references, and native-agent orchestration for Claude Code, Codex CLI, Gemini CLI, and Grok Build.
ccbeep
Zero-dependency sound notifications for Claude Code. Plays audible alerts via PermissionRequest and Stop hooks — know when Claude needs approval or has finished, without watching the terminal. macOS / Linux / Windows.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.