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/huzaifa525/claude-code-optimizer/plannpx skills add huzaifa525/claude-code-optimizer --skill plangit clone --depth 1 https://github.com/huzaifa525/claude-code-optimizerWhat 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.00026 | $0.00505 |
| Opus 5 | $0.00013 | $0.00253 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
plan 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 3d 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
Create an implementation plan for: $ARGUMENTS
Steps
-
Understand the requirement — break down what needs to be built
-
Explore the codebase — find related code, patterns, and conventions
-
Identify all changes needed:
- New files to create
- Existing files to modify
- Tests to add
- Config changes
-
Map dependencies — what must be done before what
-
Output structured plan:
## Implementation Plan: [feature]
### Overview
[1-2 sentence description of what will be built]
### Tasks
#### Phase 1: [Foundation]
- [ ] Task 1: [description]
- Files: [file1, file2]
- Pattern: follow [existing-file] as reference
- [ ] Task 2: [description]
- Files: [file1]
- Depends on: Task 1
#### Phase 2: [Core Logic]
- [ ] Task 3: [description]
- Files: [file1, file2, file3]
- Depends on: Task 1, Task 2
#### Phase 3: [Testing & Polish]
- [ ] Task 4: Write tests
- Files: [test files]
- Depends on: Phase 2
- [ ] Task 5: Update docs
- Files: [CLAUDE.md, README]
### Files Map
| File | Action | Purpose |
|------|--------|---------|
| [path] | Create/Modify | [what changes] |
### Reference Code
- [existing-file] → follow this pattern for [X]
- [existing-file] → follow this pattern for [Y]
### Risks
- [potential issues and mitigations]
### Estimated Scope
- [X] files to create
- [Y] files to modify
- [Z] tests to add
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.
- 3d ago First seen · 76 lines · 26 tokens per session scan A 4ee7c022b550
plan is a skill published in the GitHub repository huzaifa525/claude-code-optimizer (9 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 505 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
throughline
Use when the user asks to use Throughline from Codex, continue or restore Throughline memory, export read-only handoff context for a local launcher, prepare a new Codex thread handoff, summarize a captured Codex session, or check whether the Throughline Codex Stop hook captured the current session. Hide long…
critical-review
Use when you want structured feedback on a plan or document before implementation.
save
Save all session progress to status tracking files. Use when you want to checkpoint work mid-session or before ending.
code-review
Use when you want a thorough code review of files, changes, or the entire project before shipping.
implement-batch
Use when you want to implement the next batch of a plan. Handles module implementation, testing, and validation.
audit-orchestrator
Universal Pre-Scan → Analysis → Optimization → Report orchestrator for ANY project type — web apps (Astro/SvelteKit/Next), infrastructure/homelab repos, CLI tools, libraries, backend services, monorepos, data/ML projects, docs. Self-detects project type and runs the matching analysis track. Session state lives in…