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/aziontech/webkit/audit-fixnpx skills add aziontech/webkit --skill audit-fixgit clone --depth 1 https://github.com/aziontech/webkitWhat 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.00064 | $0.02464 |
| Opus 5 | $0.00032 | $0.01232 |
| Sonnet 5 | $0.00013 | $0.00493 |
| Haiku 4.5 | $0.00006 | $0.00246 |
Grade A, and why
audit-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 2d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: audit-fix
Purpose
pnpm audit --audit-level=high is a required gate in CI — the Security Scans job in .github/workflows/governance.yml (and the local pnpm run security:audit). When it exits non-zero, at least one high or critical advisory matched a package in the workspace dependency graph.
This skill takes the failing audit, finds the minimal version bump that clears every high+ advisory, applies it to the owning workspace project, and verifies the gate passes again — while honoring a strict semver policy so a fix never silently performs a risky major upgrade.
Scope discipline: --audit-level=high ignores low / moderate. Those stay reported (informational) and are not a reason to bump anything.
When to invoke
- CI's "Audit dependencies" step fails, or
pnpm run security:auditexits non-zero locally. - A dependency review surfaces a new high/critical advisory you want remediated.
Inputs
- The repo (write access limited to manifests + the lockfile).
- Optional: a captured audit log. If none is provided, the skill runs the audit itself.
Semver policy (the core guardrail)
Compare the current resolved version against the minimum patched version that clears the advisory, per the SemVer spec (https://semver.org/lang/pt-BR/). Classify the bump and act accordingly:
| Bump class | Example | Action |
|---|---|---|
patch (x.y.Z) |
1.2.3 → 1.2.9 |
✅ Apply automatically. Patches are backward-compatible bug fixes. |
minor (x.Y.z) |
10.30.3 → 10.34.4 |
⚠️ Apply, then validate carefully — frozen-lockfile install + re-audit; for runtime/build deps also run the affected governance checks (lint / type-check / storybook build). |
major (X.y.z) |
10.x → 11.x |
🚨 ALERT and ASK first (AskUserQuestion). Majors carry breaking changes — never auto-apply. Present the advisory, the current → target jump, and the blast radius (which project; runtime vs tooling). |
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.
- 2d ago First seen · 130 lines · 64 tokens per session scan A d7830dd93e9e
audit-fix is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 2,464 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
monorepo-management
Sets up or audits a monorepo workspace: tool selection, package naming, shared tooling, inter-package dependencies, selective CI, and versioning strategy. Invoked when the user asks to set up a monorepo, add a workspace, or manage multiple packages in a single repository.
bazel-monorepo-expert
Expert knowledge for managing large-scale Bazel monorepos with multiple services, shared libraries, and cross-cutting concerns. Use for workspace structure, visibility, and dependency management.
pnpm
Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
port-sacred-terminal-ui-to-react-using-same-conventions
Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…
port-sacred-terminal-ui-to-typescript-cli
Take a React Window.tsx (or any sacred component) and produce a terminal CLI screen written in TypeScript that uses Simulacrum — the sacred CLI framework in scripts/cli/lib/.