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 vinnie357/claude-skills --skill dependabot-consolidatorgit clone --depth 1 https://github.com/vinnie357/claude-skillsWrote 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/vinnie357/claude-skills/dependabot-consolidator)<a href="https://agentmods.dev/skills/vinnie357/claude-skills/dependabot-consolidator"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/dependabot-consolidator/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/vinnie357/claude-skills/dependabot-consolidator"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/dependabot-consolidator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.01580 |
| Opus 5.5 | $0.00034 | $0.00632 |
| Sonnet 5.5 | $0.00017 | $0.00316 |
| Haiku 4.5 | $0.00009 | $0.00158 |
Grade A, and why
dependabot-consolidator 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependabot Consolidator
Codifies the recipe proven on kina PR #36: collect open Dependabot PRs, consolidate into one tested branch and PR, verify with baseline-diff gates, and close out on operator approval. Single-repo, operator-supervised scope.
Scope: Dependabot only
List open Dependabot PRs with:
gh pr list --author "app/dependabot" --state open \
--json number,title,headRefName,files
Warning: never touch human-authored PRs in the same pass. The --author app/dependabot filter is the guard; verify it returns only bot-authored entries before proceeding.
Decide grouping: ecosystem and risk
Classify each PR as config-only Actions or code/package bump before creating the branch. Decision: consolidate-all vs split-actions-from-code.
- Config-only Actions bumps (
.github/workflows/*.ymlonly): validated authoritatively by real GitHub CI running on the pushed branch. Low risk; consolidate freely. - Language/package bumps (Cargo.toml, package.json, go.mod, etc.): breaking MAJORs may need local compile, test, and code changes. Higher risk; consider splitting from Actions bumps if any contain MAJOR version changes.
See references/group-by-risk.md for the full ecosystem × risk taxonomy.
Consolidation procedure
Create branch and cherry-pick each Dependabot PR head in order:
git fetch origin
git checkout -b chore/consolidate-dependabot origin/main
For each PR (ordered low-risk first, MAJOR bumps last):
git cherry-pick <pr-head-sha>
Conflict rule — keep every bump: Dependabot PRs each target a distinct dependency. When cherry-pick conflicts arise, keep both sides (each bump targets a different line/package). Do not drop either side.
Pin-style preservation: Dependabot updates pins in two styles — @v4 major tag and full commit SHA with a # vX.Y.Z trailing comment. Read the file before cherry-picking to know which style applies; preserve that style after merge.
Lockfile handling: Before assuming a lockfile needs a manual update, run git check-ignore <lockfile>. If the lockfile is tracked, commit the updated version. For Cargo: cargo update -p <dep> for the specific crate only — do not run a global cargo update.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/dependabot-collector.md 1.8 KB
- agents/dependabot-consolidator-worker.md 3.7 KB
- references/baseline-diff-verification.md 3.1 KB
- references/consolidation-algorithm.md 2.9 KB
- references/group-by-risk.md 3.0 KB
- references/local-integration-gates.md 2.5 KB
- references/merge-and-closeout.md 2.8 KB
- references/registration.md 3.0 KB
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 Changed · +3 lines 22c54c56e923
- 1mo ago First seen · 132 lines · 85 tokens per session scan A 5a0c37f41620
dependabot-consolidator is a skill published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 1,580 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
github-pr-workflow
GitHub issues and PR lifecycle: file/triage issues, carry an issue to a verified PR, branch, commit, open, CI, merge.
devops-pipeline
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance. Use when adding or auditing CI/CD to maximize local test coverage and minimize CI cost. Skip for Terraform/K8s, deployment pipelines, or non-GitHub CI providers.
gitlab-issue-to-mr
Create an automation that implements GitLab issues when a configurable trigger label is applied. Polls one or more projects deterministically, clones the default branch, starts one OpenHands conversation per label event, then commits, pushes, and opens the merge request itself.
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
commit
Delegate a single Conventional Commit.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.