agentleFS
Sign inStart free
dRafaleDdRafaleD/cybersec-skills/skills/engineering/lean-deps/SKILL.md

lean-deps

Skill2 starsChanged 56 days agoMITView on GitHub

Runs token-efficient dependency and license reviews for Cursor and Codex. Summarizes direct packages from manifests without dumping lockfiles, and flags abandoned or high-churn security-sensitive libraries. Use when the user asks for dependency review, outdated packages, license scan, or lockfile health. Do not use for exploiting package managers or publishing malware to registries.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $lean-sec deps already ran, reuse that stdout instead of scanning twice.

    line 26
  2. Very specific:

    Run summary. Note missing lockfiles, latest ranges, security-surface packages.

    line 40
  3. Very specific:

    Never paste lockfiles, npm ls, or full audit JSON.

    line 46
  4. Distinctive:

    No malicious package publishing.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Lean Deps

Manifest summary only. Do not cat lockfiles. Do not paste CVE encyclopedias.

Let SKILL_ROOT be the folder that contains this SKILL.md. Prefer python3; on Windows use py -3.

python3 "$SKILL_ROOT/scripts/lean_deps.py" summary .
python3 "$SKILL_ROOT/scripts/lean_deps.py" trim --chars 2500 path/to/out.txt

If $lean-sec deps already ran, reuse that stdout instead of scanning twice.

Mode

Default lean.

ModeBudget
leansummary + up to 8 slices; references/health.md; ≤6 findings
standardup to 16 slices; ≤10 findings
deepstill no lockfile dump; ≤16 findings

Workflow

  1. Run summary. Note missing lockfiles, latest ranges, security-surface packages.
  2. Open only the manifest, not the lockfile body.
  3. Report pin/lockfile/replace. Stop unless asked to patch.

Hard rules

  • Never paste lockfiles, npm ls, or full audit JSON. trim if a scanner already ran.
  • No malicious package publishing.
  • Cap quotes at 12 lines.

Report template

## Lean-deps (`<mode>`)

**Ecosystems:** <npm/py/go> | **Direct:** <n>

| Sev | Location | Issue | Fix |
|-----|----------|-------|-----|
| MED | package.json | no lockfile | commit package-lock; npm ci |

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free