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/smart-editnpx skills add huzaifa525/claude-code-optimizer --skill smart-editgit clone --depth 1 https://github.com/huzaifa525/claude-code-optimizerWrote 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/huzaifa525/claude-code-optimizer/smart-edit)<a href="https://agentmods.dev/skills/huzaifa525/claude-code-optimizer/smart-edit"><img src="https://agentmods.dev/badge/skills/huzaifa525/claude-code-optimizer/smart-edit.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.00020 | $0.00432 |
| Opus 5 | $0.00010 | $0.00216 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
smart-edit 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
Before making any changes for $ARGUMENTS, follow this process:
1. Find Similar Examples
- Search for existing code that does something similar
- Read at least 2 examples of the same pattern in this codebase
- Note: naming conventions, file locations, import styles, error handling
2. Check Conventions
- Read CLAUDE.md and any relevant .claude/rules/ files
- Look for linting config (.eslintrc, .prettierrc, ruff.toml, etc.)
- Check if there's a template or generator for this type of change
3. Plan the Change
- List all files that need to be created or modified
- Identify the order of changes (dependencies first)
- Note any tests that need to be added or updated
4. Implement
- Follow the exact patterns found in step 1
- Match naming, structure, and style exactly
- Add tests following the existing test patterns
5. Verify
- Run the relevant test command
- Check that no existing tests broke
- Verify the change integrates with existing code
Pre-Delivery Checklist
Before presenting the result, verify:
- At least 2 similar examples were read from the codebase
- Naming matches existing conventions (casing, prefixes, suffixes)
- File location follows existing project structure
- Import style matches the codebase (relative vs absolute, named vs default)
- Error handling follows existing patterns (not invented new ones)
- Tests added following existing test patterns
- No unrelated changes or "while I'm here" improvements
- Linter/formatter would pass on the new code
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 · 49 lines · 20 tokens per session scan A af3053c017f1
smart-edit is a skill published in the GitHub repository huzaifa525/claude-code-optimizer (9 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 432 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…