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 fix-security-auditgit 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/fix-security-audit)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/fix-security-audit"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/fix-security-audit/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/fix-security-audit"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/fix-security-audit.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.00066 | $0.01970 |
| Opus 5 | $0.00033 | $0.00985 |
| Sonnet 5 | $0.00013 | $0.00394 |
| Haiku 4.5 | $0.00007 | $0.00197 |
Grade A, and why
fix-security-audit 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 10d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments
[<path-to-project>]
- Optional. Path to the project root to audit. Defaults to the current working directory.
- Examples:
/fix-security-audit,/fix-security-audit ./packages/api
Copilot CLI note:
$ARGUMENTSdoesn't substitute in skills — include the argument inline in your prompt.
Fix security audit
Detect the package manager a JS/TS project uses, audit its dependencies for known vulnerabilities, and resolve them safely — applying the least-invasive fix first, backing up before any change, re-auditing after each step, and re-running the project's quality gates before declaring success. Never break the user's dependency tree silently.
Run every command in the project root (from $ARGUMENTS if given, else the current directory). Commands below are written shell-agnostically — discard stderr as your shell allows (2>$null in PowerShell, 2>/dev/null in bash) and do not chain with &&.
Step 1 — Detect the package manager
Check signals in order; first match wins. Report which manager was detected and the signal that decided it.
| Signal (checked in order) | Manager |
|---|---|
packageManager field in package.json (corepack) |
trust it (npm / pnpm / yarn) |
deno.json, deno.jsonc, or deno.lock present |
deno |
bun.lock or bun.lockb present |
bun |
pnpm-lock.yaml present |
pnpm |
yarn.lock and .yarnrc.yml present |
yarn berry (v2+) |
yarn.lock present (no .yarnrc.yml) |
yarn classic (v1) |
package-lock.json present, or nothing matched |
npm |
If multiple lockfiles exist, prefer the packageManager field; otherwise pick the most specific lockfile and warn the user about the ambiguity — do not guess silently. If no JS/TS project is found at all, stop and say so.
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.
- 10d ago First seen · 141 lines · 66 tokens per session scan A 215f8e6154c6
fix-security-audit is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 26d ago), licensed MIT. It adds 66 tokens to every session and 1,970 once invoked, about $0.0003 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
docs-sync
Keep project documentation in sync with code changes. Identifies which docs need updating after a PR merges or code changes, drafts the updates, and manages doc site structure (mkdocs, docusaurus, vitepress). Use when: (1) a PR just merged and docs may need updating, (2) the user says "update the docs" or "sync docs"…
project-planner
Triage ideas, problems, and feature requests into the right format: proposal doc, feature issue, or bug report. Repo-aware — discovers templates and docs structure from the current repository. Use when: (1) the user describes an idea, feature, or problem they want to track, (2) the user says "file a bug", "I have an…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
go-benchmark
Go performance benchmarking and pprof profiling specialist. ALWAYS use when writing benchmark functions (testing.B), generating or reading pprof profiles, interpreting flame graphs, finding memory allocation hotspots, comparing implementations with benchstat, or measuring ns/op / B/op / allocs/op. In Go code contexts…