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 skills add taylorleese/claude-toolz --skill resolve-github-alertsgit clone --depth 1 https://github.com/taylorleese/claude-toolzWrote 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/taylorleese/claude-toolz/resolve-github-alerts)<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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00125 | $0.04517 |
| Opus 5.5 | $0.00050 | $0.01807 |
| Sonnet 5.5 | $0.00025 | $0.00903 |
| Haiku 4.5 | $0.00013 | $0.00452 |
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 1mo 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 | 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 usemain, but some usemaster,develop, ortrunk. Rungh repo view --json defaultBranchRef --jq .defaultBranchRef.nameonce 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, andghcommands 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
- 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. - Dismiss only for confirmed false positives — Only dismiss alerts for test credentials, false positives, or transitive dependencies with no available patch.
- Create GitHub issues as last resort — Only when the fix requires human judgment or access you don't have.
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.
- 1mo ago First seen · 494 lines · 125 tokens per session scan A 5e5cfbf37591
resolve-github-alerts is a skill published in the GitHub repository taylorleese/claude-toolz (3 stars, last pushed 2mo ago), licensed MIT. It adds 125 tokens to every session and 4,517 once invoked, about $0.0005 per session on Opus 5.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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…