Audit Dependencies

Use when fixing dependency vulnerabilities, running pnpm audit, or when the audit-dependencies CI check fails.

You say
Buy it · $69 Read it before you buy $69 Written by payloadcms · unverified publisher
Context cost
2.8k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 11.2 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Use when fixing dependency vulnerabilities, running pnpm audit, or when the audit-dependencies CI check fails

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

securitytesting

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md11.2 kB · 235 lines
--- name: audit-dependencies description: Use when fixing dependency vulnerabilities, running pnpm audit, or when the audit-dependencies CI check fails user-invocable: true disable-model-invocation: true argument-hint: 'critical|high|moderate|low' ---
9# Audit Dependencies
10
11## Overview
12
13Fix dependency vulnerabilities reported by .github/workflows/audit-dependencies.sh. Prefer fixes in this order: direct dependency bump > lockfile update > pnpm override. Every override requires justification for why simpler approaches aren't feasible.
14
15## Core Workflow
16
17```dot
18digraph audit {
19 "Run audit script" [shape=box];
20 "Group by package" [shape=box];
21 "Trace dependency chain" [shape=box];
22 "Can bump direct dep?" [shape=diamond];
23 "Research breaking changes" [shape=box];
24 "Breaking changes acceptable?" [shape=diamond];
25 "Apply direct bump" [shape=box];
26 "Is version pinned or ranged?" [shape=diamond];
27 "Lockfile update" [shape=box];
28 "Apply pnpm override" [shape=box];
29 "More packages?" [shape=diamond];
30 "Present plan to user" [shape=box];
31 "Install and verify" [shape=box];
32 "Build and verify" [shape=box];
33 "Commit and create PR" [shape=box];
34
35 "Run audit script" -> "Group by package";
36 "Group by package" -> "Trace dependency chain";
37 "Trace dependency chain" -> "Can bump direct dep?";
38 "Can bump direct dep?" -> "Research breaking changes" [label="yes"];
39 "Can bump direct dep?" -> "Is version pinned or ranged?" [label="no"];
40 "Research breaking changes" -> "Breaking changes acceptable?";
41 "Breaking changes acceptable?" -> "Apply direct bump" [label="yes"];
42 "Breaking changes acceptable?" -> "Is version pinned or ranged?" [label="no"];
43 "Is version pinned or ranged?" -> "Lockfile update" [label="ranged - fix is in range"];
44 "Is version pinned or ranged?" -> "Apply pnpm override" [label="pinned - explain why"];
45 "Apply direct bump" -> "More packages?";
46 "Lockfile update" -> "More packages?";
47 "Apply pnpm override" -> "More packages?";
48 "More packages?" -> "Trace dependency chain" [label="yes"];
49 "More packages?" -> "Present plan to user" [label="no"];
50 "Present plan to user" -> "Install and verify";
51 "Install and verify" -> "Build and verify";
52 "Build and verify" -> "Commit and create PR";
53}
54```
55
56## Step-by-Step
57
58### 1. Run the Audit Script
59
60```bash
61./.github/workflows/audit-dependencies.sh $ARGUMENTS
62```
63
64$ARGUMENTS is the severity passed to the skill (defaults to high if omitted). The script runs pnpm audit --prod --json and filters for actionable vulnerabilities (those with a patched version available). high includes critical.
65
66Parse the output to build a deduplicated list of vulnerable packages with:
67
68- Package name and current version
69- Fixed version requirement
70- Full dependency chain (e.g., packages/plugin-sentry > @sentry/nextjs > rollup)
71
72### 2. For Each Vulnerable Package
73
74#### Trace the dependency chain
75
76Identify whether the vulnerable package is:
77
78- **Direct dependency**: Listed in a workspace package's package.json
79- **Transitive dependency**: Pulled in by another package
80
81#### Try direct bump first
82
83For transitive deps, walk up the chain to find the nearest package you control:
84
851. Check if bumping the **parent package** resolves the vulnerability
86 - pnpm view <parent>@latest dependencies.<vulnerable-pkg>
87 - Check intermediate versions too (the fix may exist in a minor bump)
882. If the parent bump resolves it, research breaking changes:
89 - Check changelogs/release notes
90 - Search GitHub issues for compatibility problems
91 - Review the API surface used in this repo (read the source files)
92 - Check if the version range crosses a major version boundary
933. Present findings to user with risk assessment
94
95**Parallelize research**: When multiple packages need breaking change analysis, dispatch parallel agents (one per package) to research simultaneously.
96
97#### Check if a lockfile update is sufficient
98
99Before reaching for an override, check whether the parent's version specifier is **pinned** (exact version like 3.10.3) or **ranged** (like ^2.3.1, ~4.0.3):
100
101```bash
102pnpm view <parent> dependencies.<vulnerable-pkg>
103```
104
105If the range already includes the fixed version, a lockfile update is all that's needed:
106
107```bash
108pnpm update <vulnerable-pkg> --recursive
109```
110
111No package.json changes required — the lockfile was just stale.
112
113#### Fall back to override only when justified
114
115Add a pnpm override in root package.json only when:
116
117- The parent pins an exact version that doesn't satisfy the fix
118- No version of the parent package fixes the vulnerability
119- The parent bump has high breaking change risk (major API changes, no test coverage, requires code changes across many files)
120- The user explicitly decides to defer the parent bump to a separate PR
121
122Override format: "<parent>><vulnerable-pkg>": "^<fixed-version>"
123
124**Override syntax rules:**
125
126- Use ^ ranges, not >=. >= can cross major versions and cause unexpected resolutions (e.g., "picomatch": ">=2.3.2" can resolve to 4.x).
127- pnpm only supports single-level parent scoping: "parent>pkg" works, "grandparent>parent>pkg" does not.
128- pnpm does not support version selectors in override keys: "pkg@^2" does not work.
129- If the same vulnerable package appears through many transitive paths, a global override may be needed. Be careful that it doesn't affect unrelated consumers on a different major version — use parent-scoped overrides when the package spans multiple major versions across the tree.
130- pnpm only honors overrides in the root workspace package.json. Overrides in workspace packages are ignored.
131
132Before adding any override, verify the target version exists:
133
134```bash
135pnpm view <pkg>@<version> version
136```
137
138### 3. Present Plan to User
139
140Before applying fixes, present a summary table to the user showing each vulnerability, the proposed fix strategy (direct bump / lockfile update / override), and justification. Get confirmation before proceeding.
141
142### 4. Apply Fixes
143
144- Edit package.json files for direct bumps
145- Run pnpm update <pkg> --recursive for lockfile-only fixes
146- Edit root package.json pnpm.overrides for overrides (keep alphabetical)
147- If a direct bump changes behavior, update consuming code (e.g., adding allowOverwrite: true when an API default changes)
148
149### 5. Install and Verify
150
151```bash
152pnpm install
153```
154
155If install fails due to native build errors (e.g., better-sqlite3), fall back to:
156
157```bash
158pnpm install --ignore-scripts
159```
160
161Then re-run the audit script with the same severity:
162
163```bash
164./.github/workflows/audit-dependencies.sh $ARGUMENTS
165```
166
167The audit script must exit 0. If vulnerabilities remain, check for additional instances of the same dependency in other workspace packages.
168
169### 6. Build and Verify
170
171```bash
172pnpm run build:core
173```
174
175For packages with changed dependencies, also run their specific build:
176
177```bash
178pnpm run build:<package-name>
179```
180
181### 7. Look Up CVEs
182
183For each fixed vulnerability, find the GitHub Security Advisory (GHSA):
184
185- Check https://github.com/<org>/<repo>/security/advisories for each package
186- Search the web for <package-name> GHSA <fixed-version>
187- Record: GHSA ID, CVE ID, severity, one-line description
188- Prefer GHSA links (https://github.com/advisories/GHSA-xxxx-xxxx-xxxx) over NVD links
189
190**Parallelize CVE lookups**: Dispatch parallel agents to search for CVEs across all packages simultaneously.
191
192### 8. Commit and Create PR
193
194Commit with conventional commit format:
195
196```
197fix(deps): resolve $ARGUMENTS severity audit vulnerabilities
198```
199
200Create PR using gh pr create with this body structure:
201
202```markdown
203# Overview
204
205[What the PR fixes, mention pnpm audit --prod]
206
207## Key Changes
208
209- **[Package name] in [workspace path]**
210 - [old version] → [new version]. Fixes [GHSA-xxxx-xxxx-xxxx](https://github.com/advisories/GHSA-xxxx-xxxx-xxxx) ([description]).
211 - [Why this approach: direct bump because X / lockfile update because Y / override because Z]
212 - [Any code changes required by the bump]
213
214## Design Decisions
215
216[Why direct bumps were preferred, justification for any remaining overrides]
217```
218
219## Common Mistakes
220
221| Mistake | Fix |
222| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
223| Jumping straight to overrides | Check: can you bump the parent? If not, does the semver range already allow the fix (lockfile update)? Only then override. |
224| Using >= in override ranges | Use ^ to stay within the same major version. >=2.3.2 can resolve to 4.x. |
225| Not checking pinned vs ranged | pnpm view <parent> dependencies.<pkg> — if ranged and the fix is in range, just pnpm update. |
226| Nested override scoping (a>b>c) | pnpm only supports single-level: "parent>pkg". For deeper chains, override the direct parent or use a global override. |
227| Version selectors in override keys (pkg@^2) | Not supported by pnpm. Use parent-scoped or global overrides instead. |
228| Global override affecting multiple major versions | "picomatch": ">=4.0.4" forces all picomatch to 4.x, breaking consumers that need 2.x. Scope overrides to the parent when a package spans multiple majors. |
229| Not checking all workspace packages | Same dep may appear in multiple package.json files (e.g., changelogen in both tools/releaser and tools/scripts) |
230| Overriding with a nonexistent version | Verify the target version exists with pnpm view before installing |
231| Not falling back to --ignore-scripts | Pre-existing native build failures block pnpm install; use --ignore-scripts to get lockfile updated |
232| Missing code changes for breaking bumps | If a bump changes API defaults, update the calling code |
233| Forgetting advisory links in PR | Always look up and include GHSA links for each vulnerability |
234| Applying fixes without user confirmation | Present the full plan (strategy per vuln + justification) and get confirmation before making changes |
235
In the file
SKILL.md1,394 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈60
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,740
on trigger
The instruction body, read only when the skill fires.
1.4%
of a 200k window
Ten skills this size would take about 14% of the window before you open a file.
050k100k150k200k context window

2.8k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 11.2 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md11.2 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$69 once
Audit Dependencies · MIT · payloadcms
one-time
Price$69 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$69
Referencepayloadcms/audit-dependencies

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

PA
payloadcms

Publishes on mcprush.

0 servers listed4 skills listednot claimed
Profile
Publisher
Servers0