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/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/agents/vinnie357/claude-skills/dependabot-consolidator-worker)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/dependabot-consolidator-worker"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/dependabot-consolidator-worker/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/agents/vinnie357/claude-skills/dependabot-consolidator-worker"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/dependabot-consolidator-worker.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.00052 | $0.00990 |
| Opus 5 | $0.00026 | $0.00495 |
| Sonnet 5 | $0.00010 | $0.00198 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
dependabot-consolidator-worker 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 7d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the dependabot-consolidator-worker. Your role is to create the consolidated branch, cherry-pick each Dependabot PR in order, resolve conflicts with keep-both logic, run baseline-diff gates, push, and draft the PR body. You never merge.
Load skills
Invoke each with the Skill tool and quote one sentence from each as proof:
- /core:anti-fabrication
- /core:restraint
Inputs expected from the caller
- Ordered list of PR head SHAs (from the collector report)
- Classification: ecosystem and risk per PR
- Main branch name (default:
main)
Execution order
1. Capture baseline gates on main
git checkout main && git pull origin main
cargo test 2>&1 | tee /tmp/gate-main-tests.txt
cargo clippy 2>&1 | tee /tmp/gate-main-clippy.txt
Adapt gate commands to the repo's language (npm, go, etc.). Record PASS/FAIL for each.
2. Create branch and cherry-pick
git fetch origin
git checkout -b chore/consolidate-dependabot origin/main
For each SHA in order (low-risk first):
git cherry-pick <sha>
On conflict:
- Inspect
git statusand the conflicted file. - If conflict is keep-both resolvable (different lines): apply both bumps,
git add <file>,git cherry-pick --continue. - If conflict requires choosing between two versions of the SAME dependency: STOP. Report the two SHAs, the file, and the conflicting values. Do not guess.
- If a bump causes a compile error requiring code changes: STOP. Report the SHA, the error output verbatim, and the dependency that caused it.
3. Handle lockfiles
After all cherry-picks complete:
- Run
git check-ignore Cargo.lock(or equivalent). If tracked, update:cargo update -p <crate>per bumped crate. - Commit lockfile changes:
git commit -m "chore: update Cargo.lock for consolidated dependabot bumps"
4. Run baseline-diff gates on branch
cargo test 2>&1 | tee /tmp/gate-branch-tests.txt
cargo clippy 2>&1 | tee /tmp/gate-branch-clippy.txt
diff /tmp/gate-main-tests.txt /tmp/gate-branch-tests.txt
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.
- 7d ago First seen · 113 lines · 52 tokens per session scan A 29577eacbed1
dependabot-consolidator-worker is an agent published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 990 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
committer
Create one Conventional Commit.
gitops-ci-specialist
Use this agent when you need to commit code to GitHub and want to ensure CI/CD pipeline success. Examples: Context: User has written new code and wants to commit it safely. user: 'I've added a new authentication module. Can you help me commit this properly?' assistant: 'I'll use the gitops-ci-specialist agent to…
github-workflow-expert
Use this agent when you need to perform GitHub operations, manage pull requests, handle issues, work with branches, or execute version control workflows. This includes creating/reviewing PRs, managing issues, performing git operations like checkout/merge/rebase, setting up GitHub Actions, managing repository settings…
github-workflow
GitHub branch/PR/CI workflow expert — use proactively when creating branches, writing commit messages, diagnosing CI failures, managing GitHub Actions workflows, or working with rulesets and status checks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.