resolve-github-alerts

resolve-github-alerts is a skill for Claude Code from taylorleese/claude-toolz. It costs 125 tokens per session (4,517 once invoked), scanned A, original, MIT.

A guide for resolving GitHub security alerts, including warnings about vulnerable dependencies, code problems, and exposed secrets.

In plain words
What is it for?
Use it to fix Dependabot alerts, code-scanning alerts, and secret-scanning alerts across supported package and deployment ecosystems.
Why use it?
It helps you triage and clean up security warnings across common programming-language, container, and automation setups.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the resolve-github-alerts plugin — 1 skill, 1 command shipped together

Install

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.

agentmods
npx agentmods add skills/taylorleese/claude-toolz/resolve-github-alerts
Any agent
npx skills add taylorleese/claude-toolz --skill resolve-github-alerts
Clone the repo
git clone --depth 1 https://github.com/taylorleese/claude-toolz

Made for: Claude Code.

Or install resolve-github-alerts, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

agentmods badge for resolve-github-alerts

README.md
[![agentmods](https://agentmods.dev/badge/skills/taylorleese/claude-toolz/resolve-github-alerts.svg)](https://agentmods.dev/skills/taylorleese/claude-toolz/resolve-github-alerts)
Your own site
<a href="https://agentmods.dev/skills/taylorleese/claude-toolz/resolve-github-alerts"><img src="https://agentmods.dev/badge/skills/taylorleese/claude-toolz/resolve-github-alerts.svg" alt="Measured on agentmods" height="20"></a>
Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,517 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00125 $0.04517
Opus 5 $0.00063 $0.02259
Sonnet 5 $0.00025 $0.00903
Haiku 4.5 $0.00013 $0.00452

Measured 5d ago against content hash 5e5cfbf37591, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

resolve-github-alerts scanned grade A with 1 finding 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 5d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

| Command injection | Use `subprocess.run()` with list args, never `shell=True` with user input |
plugins/resolve-github-alerts/skills/resolve-github-alerts/SKILL.md · 494 lines

How it starts

The opening of the file, as written. The whole thing — 494 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resolve GitHub Alerts

This skill resolves all GitHub security alerts: Dependabot alerts, code scanning alerts, and secret scanning alerts.

Constants

  • Label: automated/resolve-github-alerts
  • Branch: automated/resolve-github-alerts
  • Base branch: detect at runtime — do not hardcode main. Most repos use main, but some use master, develop, or trunk. Run gh repo view --json defaultBranchRef --jq .defaultBranchRef.name once at the start of execution and use the result everywhere a base branch is needed (PR creation, branch creation, etc.).

Setup

At the start of execution, derive the GitHub owner and repo. Use git remote get-url origin from the current working directory (works in both the main checkout and git worktrees):

OWNER_REPO=$(git remote get-url origin | sed -E 's#.*(github\.com[:/])##;s/\.git$//')
OWNER=${OWNER_REPO%/*}
REPO=${OWNER_REPO#*/}

Use $OWNER and $REPO in all gh CLI commands below.

Worktree Awareness

This skill may run inside a git worktree. Observe these rules:

  • Derive repo root from git rev-parse --show-toplevel, never hard-code a path.
  • All file reads/edits must use paths relative to the worktree root, not the main checkout.
  • git remote, git fetch, git push, and gh commands work unchanged in a worktree because they share the main repo's remote configuration.
  • Do not run git worktree add/remove — the caller manages the worktree lifecycle.

Resolution Priority

  1. Fix the root cause in code — All fixes must be committed as code changes: dependency upgrades in the project's manifest/lockfiles (e.g. requirements*.{in,txt}, pyproject.toml, poetry.lock, uv.lock, package.json, Cargo.toml, go.mod), Dockerfile base image tags, GitHub Actions versions, or application code fixes in the project's source tree. Never apply ad hoc fixes via manual steps. Never add lint exclusions or scanner ignores.
  2. Dismiss only for confirmed false positives — Only dismiss alerts for test credentials, false positives, or transitive dependencies with no available patch.
  3. Create GitHub issues as last resort — Only when the fix requires human judgment or access you don't have.

Read the full file on GitHub · 494 lines

Changes

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.

  1. 5d ago First seen · 494 lines · 125 tokens per session scan A 5e5cfbf37591

Subscribe to this mod's changes

resolve-github-alerts is a skill published in the GitHub repository taylorleese/claude-toolz (3 stars, last pushed 29d ago), licensed MIT. It adds 125 tokens to every session and 4,517 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens