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 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/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.
<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="Reviewed on agentmods" width="80" 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.00033 | $0.00997 |
| Opus 5.5 | $0.00013 | $0.00399 |
| Sonnet 5.5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
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 1mo 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 — 99 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:
$ARGUMENTSdoes not substitute in skills; include the argument inline in your prompt.
Optimize: $ARGUMENTS
Analyze code for performance bottlenecks. Only flag a finding when the fix meets BOTH of these criteria:
- The fix removes a measurable cost: algorithmic complexity drop (e.g., O(n^2) -> O(n)), one fewer DB/HTTP round-trip per call, one fewer reactive re-render per interaction, >= 5% bundle-size reduction, or eliminated memory 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 are not 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 onlyfull: entire codebase under the current working directory- file path: analyze that specific file (stop if file does not exist)
- anything else: treat as a component or module name and locate it
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.
- 1mo ago Changed · +25 lines · +6 tokens per session 312307d7c801
- 1mo 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 18d ago), licensed MIT. It adds 33 tokens to every session and 997 once invoked, about $0.0001 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-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.
windbg-user-heap-corruption-investigation
Use when an app, service, or user-mode driver host heap fails or Application Verifier detects corruption; inspect history and bounds. Not for kernel pool corruption or ordinary OOM.
frontend-testing-debugging
This skill should be used when user asks to "debug this UI", "verify a rendered frontend change", or "check responsive layouts". Diagnose visual and interaction problems, compare reference screenshots, and reuse project QA journeys when available.
asc-crash-triage
Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.
spk-admin-setup-doctor
Install, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.