Work on Repeat
Menu

Example routine

Dependency vulnerability triage

Separate exploitable dependency advisories from noise and propose an upgrade order.

Use this routine

Suggested rhythm

Weekly

0 8 * * 2

America/Los_Angeles

Expected result

A triaged advisory list split into exploitable, upgrade-soon, and noise, with a proposed upgrade order and evidence for each call.

Built for

Security · Engineering

Works with

  • GitHub

What the routine does

Review open dependency and security advisories for the connected repository {{repository}}. For each finding, check whether the vulnerable path is actually reachable in this codebase, group the results into exploitable, upgrade-soon, and noise, and propose a concrete upgrade order with the smallest safe version bumps. Open tracking issues only through explicitly approved tools and never push dependency changes directly.

Inputs

  • Repository{{repository}}

    The repository whose dependencies to triage.

    Example: acme/web-app

Required MCP capabilities

  • Read repository content
  • Read security advisories

Permission boundary

Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.

More security routines