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/nortonx/ai-tooling-free/optimizenpx skills add nortonx/ai-tooling-free --skill optimizegit clone --depth 1 https://github.com/nortonx/ai-tooling-freeWrote 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/nortonx/ai-tooling-free/optimize)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/optimize"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/optimize.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.1 | $0.00027 | $0.00771 |
| Opus 5 | $0.00014 | $0.00385 |
| Sonnet 5 | $0.00005 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
optimize 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments
[branch | backend | frontend | <path>]
- Optional. Picks the analysis scope; the skill prompts with a numbered menu if omitted.
- Examples:
/optimize branch,/optimize backend,/optimize src/services/payments.ts
Copilot CLI note:
$ARGUMENTSdoesn't substitute in skills — include the argument inline in your prompt.
Optimize: $ARGUMENTS
Analyze for performance bottlenecks. Only flag a finding when the fix meets BOTH of these:
- The fix removes a measurable cost — algorithmic complexity drop (e.g., O(n²) → O(n)), one fewer DB/HTTP round-trip per call, one fewer React re-render per interaction, ≥ 5% bundle-size reduction, or eliminated allocation in a hot path.
- The fix is ≤ 30 lines of code change OR is a one-line config/index change.
Skip:
- Stylistic-only changes (rename, reorder, reformat).
- Micro-optimizations whose impact you cannot estimate.
- "Defensive" caching of values that aren't measured to be hot.
- Anything that adds a new dependency unless the dependency replaces ≥ 100 lines of in-repo code.
Scope
If $ARGUMENTS is empty, stop and ask the user which scope to analyze before doing anything else. Present this numbered menu verbatim and wait for a reply:
Which scope should I analyze?
1. branch — diff between this branch and main/master
2. backend — server-side code only (API, DB, services)
3. frontend — client-side code only (components, bundles, assets)
4. <file path> — a specific file (e.g. src/foo.ts)
5. <component> — a component or module name
Otherwise interpret $ARGUMENTS as:
branch— diff between this branch andmain/masterbackend— server-side code onlyfrontend— client-side code only- file path — analyze that file
- anything else — treat as a component or module name and locate it
fullor explicit omission — full codebase
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.
- 5d ago First seen · 74 lines · 27 tokens per session scan A 868ca6dac9c9
optimize is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 21d ago), licensed MIT. It adds 27 tokens to every session and 771 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
roblox-build-fix
Use to systematically diagnose and fix Rojo, Wally, Selene, StyLua, Luau-LSP, TestEZ, or other Roblox build / toolchain failures. Use when the user says "the build is broken", "Rojo won't sync", "Wally install fails", "selene reports", "luau-lsp errors", "tests fail", or any toolchain-level error blocks progress.
node-zombie-guardian
Use when diagnosing stale or orphaned Node.js processes launched by VCO, auditing ownership/liveness, or safely simulating cleanup without touching external Node workloads.
providing-performance-optimization-advice
Produce a prioritized performance-optimization roadmap across frontend, backend, and infrastructure. Use as an explicit/manual helper after bottlenecks are known or suspected, not as the owner of regression detection, profiling capture, or test execution.
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
code-cleanup
Detect stale TODOs, unused imports, and dead code.