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 infohata/mind-vault --skill dependabot-triagegit clone --depth 1 https://github.com/infohata/mind-vaultWrote 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/infohata/mind-vault/dependabot-triage)<a href="https://agentmods.dev/skills/infohata/mind-vault/dependabot-triage"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/dependabot-triage/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/infohata/mind-vault/dependabot-triage"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/dependabot-triage.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.00190 | $0.03556 |
| Opus 5 | $0.00095 | $0.01778 |
| Sonnet 5 | $0.00038 | $0.00711 |
| Haiku 4.5 | $0.00019 | $0.00356 |
Grade A, and why
dependabot-triage 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 10d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dependabot-triage
A workflow for processing 5–20 accumulated Dependabot PRs as one coherent sweep instead of one-PR-at-a-time fatigue. The non-obvious pieces are (1) two PRs touching the same package are not necessarily duplicates when the repo has multiple requirements files served by separate dependabot ecosystems, and (2) risk-tier batching with one commit per dep preserves git bisect even when the PR ships a bundle.
Vendored-static variant. If the repo tracks vendored browser assets via a synthetic
package.json(npm ecosystem) + a re-vendor CI workflow that commits refreshedstatic/bytes onto the PR branch, the sweep has its own failure modes (PRs stuckunstableon stale mapsrcpaths; major bumps need arevendor-mapsrc change, not a byte refresh; consolidation as the unblock when CI is wedged and the bot can't recreate). Readreferences/VENDORED_STATIC_REVENDOR.mdalongside the steps below.
When to use
TRIGGER when:
- A pile of Dependabot PRs has accumulated and the user asks for a roadmap to merge them.
- Two PRs look like duplicates but the user is unsure whether to close one.
- A version-scheme jump (e.g. pre-1.0 → post-1.0, or
0.0.x → 1.x.x) is mixed in with low-risk patch bumps and the user wants to know how to split them. - A dep PR floor-bumps a package that's actively used somewhere subtle (Vertex / OpenAI / Stripe / etc.) — needs targeted smoke beyond the test suite.
SKIP when:
- Single Dependabot PR with no version-scheme jumps and no actively-used SDK — just merge it.
- Repo has only one requirements file and one ecosystem — the multi-ecosystem nuance doesn't apply, simpler triage.
- Security-only batch where every PR must merge same day — risk-tier batching is overkill, ship them as one or sequentially.
Pattern
1. Survey
gh pr list --author "app/dependabot" --state open --limit 100 \
--json number,title,headRefName,mergeable,labels
What ships with it
1 file 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.
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.
- 10d ago First seen · 195 lines · 190 tokens per session scan A 10d91a12a9b8
dependabot-triage is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 190 tokens to every session and 3,556 once invoked, about $0.0010 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-08-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.