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 smart-fixgit 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/smart-fix)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/smart-fix"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/smart-fix/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/smart-fix"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/smart-fix.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.00018 | $0.00664 |
| Opus 5 | $0.00009 | $0.00332 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
smart-fix 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 9d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments
<issue description>
- Required. Free-text description of the bug, perf issue, security concern, or feature ask.
- Examples:
/smart-fix login throws NullReferenceException on empty email,/smart-fix the search page takes 8s to render
Copilot CLI note:
$ARGUMENTSdoesn't substitute in skills — include the argument inline in your prompt.
Intelligently fix: $ARGUMENTS
Route the request to the right skill based on the keywords in the description. Apply rules in order — first match wins.
Routing table
Trigger keywords (case-insensitive) in $ARGUMENTS |
Route to |
|---|---|
throws, error, exception, crash, null, undefined, NaN, fails, broken, wrong output, regression |
Treat as a bug — reproduce it first, isolate the root cause, write a failing regression test, then fix. (If the superpowers plugin is installed, invoke superpowers:systematic-debugging instead.) |
slow, takes Xs, Xms, lag, freezes, hangs, memory leak, OOM, bundle size, re-render |
Invoke /optimize with the file or area from the description as scope |
CVE, vuln, vulnerability, XSS, SQLi, injection, auth bypass, leak, secret, token, unsafe |
Perform an OWASP-Top-10-oriented security review of the affected area and propose the patch; if a specific CVE/advisory is named, also propose the dependency or code patch |
add, support, new, enable, allow, should be able to, as a user I want |
Treat as feature work — clarify intent and requirements with the user before coding, then implement. (If the superpowers / feature-dev plugins are installed, invoke superpowers:brainstorming then feature-dev:feature-dev instead.) |
| None of the above match | Stop and ask the user to clarify which of the four buckets it falls under (bug, performance, security, feature) — do not guess |
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.
- 9d ago First seen · 41 lines · 18 tokens per session scan A 1452f310bc04
smart-fix is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 25d ago), licensed MIT. It adds 18 tokens to every session and 664 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
log-analyzer
Senior-SRE log analysis specialist. Use when investigating incidents from logs, triaging error spikes, extracting timelines, correlating distributed traces, or separating signal from noise across plain-text, JSON (slog/zap), syslog, journald, container, and Kubernetes logs. ALWAYS use when the user asks to "analyze…
incident-postmortem
Incident post-mortem specialist for writing blameless post-mortems, extracting timelines from logs/events, conducting root cause analysis (5-Why, fishbone), classifying severity, and generating tracked action items. ALWAYS use when writing a post-mortem, reviewing an incident, extracting a timeline, performing root…
systematic-debugging
Use when debugging, diagnosing, or investigating any bug, test failure, flaky test, race condition, unexpected behavior, build failure, production incident, third-party breakage, root cause analysis, or performance regression before proposing fixes.
systematic-debugging
Use when a bug is non-obvious or has resisted quick fixes — applies a 4-phase root cause analysis to find and permanently resolve the issue rather than patching symptoms.
cpp-debugging
Use when a C++ failure involves memory lifetime, undefined behavior, native crashes, or debugger-only state — debug with symbols, sanitizers, and platform-native debuggers before patching symptoms.
fix-github-issue
Use when you have a GitHub Issue number or link and want it resolved end-to-end — reads the issue, locates the bug, applies a fix, writes tests, and opens a PR from the terminal.