git:20260813.f1ed50f to git:20260813.199d770

9 added, 1 removed. Audit A to A.

---

name: "Repo: Analyse Package Deps"

- description: "{{ 𝛀𝛀𝛀 }} Investigate this repo's dependencies in detail"

+ description: "Investigate this repo's dependencies in detail"

when_to_use: "When auditing dependency health — outdated packages, security advisories, a specific package that looks suspect — rather than eyeballing package.json."

model: sonnet

effort: high

+ metadata:

+ glyph: ᛊ

+ family: project

disable-model-invocation: true

+ # Forked into a read-only Explore agent: a self-contained investigation whose

+ # large read/web footprint stays out of the main context. $ARGUMENTS carries

+ # the concerning dep when there is one.

+ context: fork

+ agent: Explore

allowed-tools: ["Read", "Glob", "Grep", "Bash(~/.claude/library/scripts/deps-dump.sh:*)", "WebSearch", "WebFetch"]

arguments: ["dep"]

argument-hint: "[package of concern (optional)]"

---

# Repo Package & Dependency Analysis

Provide an in-depth analysis of this codebase's package dependencies, particularly $ARGUMENTS.

</overview>

<steps>

1. Run `"$HOME"/.claude/library/scripts/deps-dump.sh` — it detects the package manager from lockfiles and dumps declared versions, outdated report and audit output in one pass. Analyse that dump rather than orchestrating the package-manager CLIs yourself.

2. For anything the dump flags (or $ARGUMENTS names), check deprecation notices & security advisories online.

3. Suggest fixes and updates, ordered by risk.

</steps>