Dependabot starts opening update pull requests for agent skills and prompts

GitHub announced Dependabot support for Agent Package Manager dependencies.

**Dek:** GitHub now tracks supported Git dependencies in Agent Package Manager manifests. The update makes shared agent instructions easier to maintain and gives teams a familiar place to review changes.

GitHub added Agent Package Manager support to Dependabot version updates on November 3. Repositories that declare agent skills, prompts or instructions through APM can now receive pull requests when supported Git dependencies have newer versions. Dependabot updates the manifest and refreshes its lockfile if one is present. The feature is generally available across GitHub.com plans. GitHub lists Enterprise Server 3.24 as the intended server release. [GitHub announcement](https://github.blog/changelog/2026-11-03-dependabot-version-updates-support-agent-package-manager/)

A new dependency to put under review

An agent package can influence how a coding assistant behaves long after the package was first adopted. A shared skill might tell the assistant which test suite to run. An instruction file might describe where release artifacts belong, or a reusable prompt might specify what information a pull request review should collect. When several repositories depend on the same package, the instructions can be maintained centrally while each repository keeps control over when it accepts an update.

The new support uses Dependabot’s existing configuration. A repository adds an APM entry to its Dependabot configuration, identifies the directory containing `apm.yml` and chooses a schedule. A resulting pull request gives the repository maintainers a place to see which dependency moved and inspect the proposed revision. GitHub says the integration regenerates `apm.lock.yaml` when the repository already has one. The underlying package manager still defines what goes into the dependency tree. [GitHub announcement](https://github.blog/changelog/2026-11-03-dependabot-version-updates-support-agent-package-manager/) · [Supported ecosystems](https://docs.github.com/en/code-security/reference/supply-chain-security/supported-ecosystems-and-repositories)

Version updates still need a policy

GitHub specifies version updates for APM. That means Dependabot can propose moving an eligible dependency to a newer version on a schedule. The APM integration does not deliver the separate Dependabot security-update function. A successful update also says little about whether a prompt or instruction change fits the receiving repository. Versioning makes changes visible and reproducible, while a review establishes whether those changes are appropriate. [GitHub announcement](https://github.blog/changelog/2026-11-03-dependabot-version-updates-support-agent-package-manager/)

One example is a package that used to ask a coding assistant to run a local test command. A later revision could add a step that requires a network connection, calls an external tool or handles data the previous release never needed. The lockfile change can help a maintainer identify the new revision. Reading that revision and running the normal agent workflow against a representative task exposes what the updated instructions actually ask the assistant to do.

A repository with private dependencies should also verify that Dependabot can read the source it needs. GitHub’s ecosystem documentation notes that version resolution may require access to the upstream private repositories, with support depending on the ecosystem and source. A failed update can therefore point to a resolution or access problem instead of a missing upstream release. [Supported ecosystems](https://docs.github.com/en/code-security/reference/supply-chain-security/supported-ecosystems-and-repositories)

For organizations already reviewing dependency updates, the useful change is that agent packages can enter the same pull request process as application dependencies. Whether the change is one line of prose or a new package revision, it is worth assessing the behavior it changes and which agent sessions will pick it up.