Intercept dependency additions

Every new dependency is a trust decision - catch it at the source.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Hook the dependency-adding actions. Identify every way the agent can add a dependency: package-manager install commands (pip install, npm/yarn add, etc.), direct edits to manifests (requirements.txt, package.json, pyproject, go.mod), and lockfile edits. Route these through a supply-chain gate before they take effect: parse out the package name(s) and version(s) being added, and pause for the checks (next steps) rather than executing immediately. Distinguish adding a NEW dependency (full gate) from updating an existing reviewed one (lighter path). Ensure no install path bypasses the gate - including the agent writing a manifest and running install as separate steps. Verify by having the agent attempt an install and confirming the gate intercepts it.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

All dependency-adding paths intercepted before taking effect.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Installs and manifest/lockfile edits both caughtNew vs existing dependency distinguishedWrite-then-install evasion covered

Do not continue if…

! Letting the agent install anything it names, hallucinations included
! Slopsquatting: installing a malicious lookalike of a real popular package
! No vulnerability scanning, so known-CVE packages ship
! Manifest edited but lockfile not updated, so installs drift from review

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

The agent edited the manifest then installed, dodging the gate. Gate on the manifest/lockfile change too, not just the install command - and treat installing after a just-made manifest edit as the same reviewable event.