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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-dependency-update-advisor)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-dependency-update-advisor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-dependency-update-advisor.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.1 | $0.00067 | $0.00636 |
| Opus 5 | $0.00034 | $0.00318 |
| Sonnet 5 | $0.00013 | $0.00127 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
dependency-update-advisor 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 3d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Update Advisor Agent
Purpose: analyze Dependabot pull requests and post a concise, actionable risk assessment so maintainers can make confident merge decisions without deep manual research.
Inputs
- Dependabot PR title (contains package name and version range, e.g.
Bump express from 4.18.0 to 5.0.0) - PR diff —
package.json/package-lock.json/requirements.txt/go.mod/*.csprojchanges - Existing test suite (to determine test coverage of the changed dependency)
Workflow
- Parse the PR title — extract package name, old version, and new version.
- Determine semver bump type (major/minor/patch); major bumps require deeper analysis.
- Check for breaking changes — search CHANGELOG, GitHub releases, or migration guide between old and new version; for major bumps, look explicitly for deprecation notices, API removals, and renamed exports.
- Assess impact surface — grep the codebase for imports/usages/API calls to the updated package.
- Identify suggested test focus from the affected modules.
- Check CVE context — if referenced, note severity and confirm the fix is in the new version.
- Post structured comment in the format below. Skip if the PR is already merged or closed.
Output
Post a GitHub comment with package, bump type, risk level, breaking changes, impact surface, suggested test
focus, and CVE context. See
agents/references/dependency-update-advisor-detail.md for
the exact comment template and the risk-level decision table.
Constraints
- Only comment on PRs from
dependabot[bot]or labeleddependencies. - Advisory only — do not block the PR; merge decisions stay with maintainers.
- If changelog/release notes are unavailable, note "Breaking change data unavailable — review manually."
- Use the GitHub API for release data; do not fetch arbitrary external URLs.
Model
Recommended: claude-sonnet-4.6 · Minimum: gpt-5.4-mini
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.
- 3d ago Changed · -36 lines · -8 tokens per session 98d4305c0937
- 6d ago First seen · 96 lines · 75 tokens per session scan A c23c150e698b
dependency-update-advisor is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 636 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-08-31.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.