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.
git 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/commands/taylorleese/claude-toolz/resolve-github-alerts)<a href="https://agentmods.dev/commands/taylorleese/claude-toolz/resolve-github-alerts"><img src="https://agentmods.dev/badge/commands/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/commands/taylorleese/claude-toolz/resolve-github-alerts"><img src="https://agentmods.dev/badge/commands/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.00021 | $0.00286 |
| Opus 5.5 | $0.00008 | $0.00114 |
| Sonnet 5.5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
resolve-github-alerts 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 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.
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.
What it actually says
Resolve every open GitHub security alert in the current repository and submit the fixes as a single pull request.
Invoke the resolve-github-alerts:resolve-github-alerts skill via the Skill tool. It owns the full workflow:
- Triage — enumerate Dependabot, code scanning, and secret scanning alerts.
- Detect — identify the repo's ecosystems (pip / pip-tools / poetry / uv / npm / yarn / pnpm / cargo / go-modules / Docker / GitHub Actions) and its verify commands.
- Fix — repair failing Dependabot PRs, bump vulnerable dependencies, recompile lockfiles, and remediate code and secret scanning alerts.
- Verify — run the project's own lint and test commands before proposing anything.
- Submit — open one pull request with all fixes, for manual review.
$ARGUMENTS, when present, narrows the scope — e.g. dependabot only, skip docker, or a specific advisory ID. Pass it to the skill verbatim.
After the skill returns, summarize: which alerts were resolved, which were left and why, and the PR URL.
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 · 19 lines · 21 tokens per session scan A 7b761b155f24
resolve-github-alerts is a command published in the GitHub repository taylorleese/claude-toolz (3 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 286 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
codex-review
Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.