Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/authgear/authgear-server/update-depsnpx skills add authgear/authgear-server --skill update-depsgit clone --depth 1 https://github.com/authgear/authgear-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/authgear/authgear-server/update-deps)<a href="https://agentmods.dev/skills/authgear/authgear-server/update-deps"><img src="https://agentmods.dev/badge/skills/authgear/authgear-server/update-deps.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00039 | $0.03131 |
| Opus 5 | $0.00019 | $0.01566 |
| Sonnet 5 | $0.00008 | $0.00626 |
| Haiku 4.5 | $0.00004 | $0.00313 |
Grade A, and why
update-deps scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
8 near-identical copies found in the catalogue:
- amazon-alexa — 86% identical, 780 lines differ
- amazon-alexa — 86% identical, 780 lines differ
- amazon-alexa — 86% identical, 780 lines differ
- amazon-alexa — 86% identical, 780 lines differ
- amazon-alexa — 86% identical, 780 lines differ
- amazon-alexa — 84% identical, 780 lines differ
- amazon-alexa — 81% identical, 785 lines differ
- amazon-alexa — 81% identical, 785 lines differ
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit and fix dependency vulnerabilities in this project. Follow the steps below in order.
Step 1: Go Vulnerability Check
Run govulncheck in every Go module in the repository:
make govulncheck
cd custombuild && make govulncheck
cd e2e && make govulncheck
cd k6 && make govulncheck
cd packagetracker && make govulncheck
Use the module's own make govulncheck target if it exists; otherwise run go tool govulncheck ./... from that module root.
Parse the output:
- If there are no vulnerabilities, note it and move on.
- If there are vulnerabilities, for each affected module:
- Run
go list -m -u <module>to find the latest available version. - Compare the current version with the latest version:
- If the major version changes (e.g.
v1.x.x→v2.x.x), this is a major version upgrade. Generate a Breaking Change Report for it (see below), defer the upgrade, and continue with any other patchable work. - If only minor/patch version changes, proceed automatically.
- After all patchable fixes are applied and any deferred major upgrades have been presented to the user for a decision, run
go get <module>@latestthengo mod tidyin all relevant directories:././custombuild./e2e./k6./packagetracker
- Run
Important:
go get <module>@latestis for Go module dependencies only. Do not use it to change the Go toolchain version.- If the requested fix is a Go version bump, update the repository's Go version files and generated inputs directly instead of trying to solve it with
go get:flake.nix.tool-versionsgo.modcustombuild/go.mode2e/go.modk6/go.modpackagetracker/go.mod.tplcustombuild/cmd/authgearx/Dockerfilecustombuild/cmd/portalx/Dockerfilecmd/portal/Dockerfilecmd/authgear/Dockerfileonce/partial.dockerfile- regenerate
once/Dockerfilewithmake once/Dockerfile - run
make go-mod-tidy
- If a Go version bump is needed, verify the repository-specific generation and build steps after editing the version files. Do not commit a toolchain bump that only changes
go.modwithout updating the other affected files.
Breaking Change Report for Go (major version bumps) must include:
- Module name, current version → proposed version
- Link to the module's changelog or migration guide if available (check the module's repository)
- Known incompatibilities (import path changes, removed/renamed symbols)
- Note that the upgrade is deferred until the end of the patchable-fix pass, then ask: "Do you want to apply this major version upgrade? (yes/no)"
After updating Go deps:
- Run
make buildorgo build ./...to verify the build. - If the build breaks, report the compiler errors and ask the user how to proceed. Do not commit.
- If vulnerabilities cannot be fixed (no fix available), note them in an Unfixable Issues Report and notify the user.
- If fixes were applied and build passes, stage and commit all affected Go module files, including
go.sum,go.mod,custombuild/go.sum,custombuild/go.mod,e2e/go.sum,e2e/go.mod,k6/go.sum,k6/go.mod, andpackagetracker/go.sum/packagetracker/go.modwhen they change, with commit message:chore: fix Go dependency vulnerabilities
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 182 lines · 39 tokens per session scan A 16a67a2ee1f0
update-deps is a skill published in the GitHub repository authgear/authgear-server (2,021 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 3,131 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
auth0-docs
Auth0 — identity platform: auth flows, Universal Login, SSO, identity providers, MFA, RBAC, Actions, tokens.
zeroid
MANUAL TRIGGER ONLY: invoke only when user types /zeroid. Identity infrastructure for AI agents — register identities, issue tokens, delegate to sub-agents, revoke credentials, and manage credential policies via the Zeroid REST API.
zeroid
Identity infrastructure for AI agents — register identities, issue tokens, delegate to sub-agents, revoke credentials, manage policies.
auth-oauth
Implements and reviews OAuth 2.0/2.1 flows following RFC 6749, RFC 9700 (BCP), and PKCE (RFC 7636). Use when implementing authorization code flow, token handling, client registration, or securing OAuth endpoints.
schema
Database schema rules for QAuth. Use when working with the identity model, Drizzle ORM, migrations, repositories, or claim resolution. Reflects the CURRENT shipped schema — the identifier-abstraction model (ADR-002, IMPLEMENTED via Epic.
fastify
Fastify usage for QAuth — plugin authoring (encapsulation, decorators, lifecycle), route schemas with the Zod type provider, production/reverse-proxy setup, and the Fastify version/CVE requirement. Use when adding or modifying @qauth-labs/fastify-plugin- libraries, auth-server routes, or deployment config.