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 agentmods add commands/dsswift/ion/resolve-dependabot-prsgit clone --depth 1 https://github.com/dsswift/ionWrote 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/dsswift/ion/resolve-dependabot-prs)<a href="https://agentmods.dev/commands/dsswift/ion/resolve-dependabot-prs"><img src="https://agentmods.dev/badge/commands/dsswift/ion/resolve-dependabot-prs.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.02240 |
| Opus 5 | $0.00017 | $0.01120 |
| Sonnet 5 | $0.00007 | $0.00448 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
resolve-dependabot-prs 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 today.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the /resolve-dependabot-prs command. Your job is a two-phase workflow:
- Analyze (read-only) — enumerate the repo's open Dependabot PRs, assess each (scope, bump, CI, risk), decide a merge/close order, and emit a terse summary table to the user.
- Plan (enter planning mode) — write a resolution plan whose steps ARE the executable sequence (rebase → merge → optional follow-up PR → resume the chain → close-for-High), ordered per the analysis. The user reviews and approves the plan through the normal plan-approval flow; the agent executes it afterward.
The user drives the loop and approves the plan. This command does not merge, rebase, close, comment, commit, or push anything. It analyzes, summarizes, and produces a reviewable plan.
Hard rules.
- During the analysis pass and during planning: no merge, no rebase, no
gh pr comment, no commit, no push, no source edits. Analysis is read-only; planning only writes the plan file. - User-facing output is intentionally terse: a single "Running the Dependabot PR analysis…" notice, then the summary table, then the short special-case blurb. No lecture. No per-PR prose for trivial bumps. The plan artifact carries all execution detail.
- The actual rebase / merge / close / follow-up steps are written into the plan, not performed by this command. They execute only after the user approves the plan.
- If there are zero open Dependabot PRs, report "No open Dependabot PRs." and stop — do not enter planning mode.
Step 0: Announce
Emit exactly one short line to the user before doing the work:
Running the Dependabot PR analysis…
Do not narrate each command as you run it. The next thing the user should see is the summary table.
Step 1: Enumerate open Dependabot PRs
gh pr list --author "app/dependabot" --state open --json number,title,headRefName,labels,createdAt,url
Belt-and-suspenders: the Dependabot author handle can differ across repos. Also enumerate by the dependencies label and union the results:
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.
- today Changed · +1 lines 3f855691a523
- 5d ago First seen · 159 lines · 35 tokens per session scan A c7127c653469
resolve-dependabot-prs is a command published in the GitHub repository dsswift/ion (4 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 2,240 once invoked, about $0.0002 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 commands, from other repositories
memory-self-review
Mine recent agent history (claude-mem + usage stats) for recurring failures and repeated patterns, audit MEMORY.md health, and PROPOSE (never apply) CLAUDE.md/memory edits for human approval.
code-review
Provide a code review for the given pull request.
echo
This is a placeholder command definition for plugin framework tests.
dashclaw-retire-legacy
Officially retire the published dashclaw/legacy Node SDK the safe way — deprecate now, delete at v5 — without breaking external npm consumers. Drives the legacy-sdk-deprecation-sweep workflow.
dashclaw-quality
Recurring find-and-fix quality pass over the whole DashClaw app — browser smoke (frontend-verify) + code gates → triage → parallel worktree fixes → verify → ship. The goal prompt that drives the dashclaw-find-and-fix workflow.
apply-self-review
Apply the approved improvements from the latest memory-self-review PROPOSAL. Auto-applies the safe, reversible doc/memory edits (with backups); queues code/config/rule-rewrite edits for an explicit go. Never commits or pushes.