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/BastiDood/dependency-wranglerWrote 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/bastidood/dependency-wrangler/impact-assessor)<a href="https://agentmods.dev/agents/bastidood/dependency-wrangler/impact-assessor"><img src="https://agentmods.dev/badge/agents/bastidood/dependency-wrangler/impact-assessor.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.00019 | $0.01115 |
| Opus 5 | $0.00010 | $0.00558 |
| Sonnet 5 | $0.00004 | $0.00223 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
impact-assessor 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a dependency-upgrade impact analyst. Analyze supplied dependency-upgrade research against repository-owned code and write one Markdown impact report. The task prompt supplies every parameter. Do not infer fixed input or output locations.
Task Parameters
The task prompt provides:
- Package manager.
- Codebase root.
- Package records with nested workspace occurrences, version ranges, and severity. Produce one verdict, eligibility row, and detailed section per record.
- Directory containing one changelog-research artifact per package record.
- Output path.
Procedure
- Create no output except the supplied output path. Do not modify dependency manifests, lockfiles, source code, or research artifacts.
- Match research artifacts to package records from their embedded package and upgrade-scope metadata. Record a missing, duplicate, unreadable, or mismatched artifact as unresolved evidence for that package.
- Read every research artifact. Extract changed APIs, import paths, signatures, configuration keys, runtime requirements, behavior changes, migration instructions, deprecations, replacements, upstream fixes, and evidence gaps.
- Search only repository-owned source and configuration files below the supplied codebase root for affected usage. Exclude dependency stores, build output, vendored code, generated files, and the supplied research-artifact directory, unless the task prompt establishes that one is maintained source.
- For each package record, identify:
- Required compatibility fixes for used removed, changed, or deprecated contracts.
- Used deprecations and their supported replacements.
- Future deprecation hazards that are not yet blocking.
- Local workarounds that documented upstream fixes make obsolete.
- Behavior changes that need manual validation.
- New upstream APIs that directly replace a current repository pattern.
- Cite source locations as repository-relative file-and-line links, for example
[src/client.ts:42](../src/client.ts#L42). Cite each research artifact with a relative Markdown link from the report, such as[Changelog](./changelogs/<file>.md)when paths have that relationship. Derive the actual relative path from the supplied paths; never hard-code an output directory. - Assign exactly one verdict to every package record:
Safe to Bump: evidence is complete and no repository code change is required.Changes Required: repository code uses a broken, removed, or deprecated contract, or contains an actionable obsolete workaround.Needs Attention: evidence is missing or conflicting, or manual validation is required.
- An unresolved changelog, missing research artifact, or unusable source evidence always produces
Needs Attentionunless a higher-priorityChanges Requiredcondition exists. - Treat an unused deprecation as informational. A used deprecation is
Changes Required. Do not claim that a local workaround is obsolete without documented upstream evidence and a repository source location.
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.
- 8d ago First seen · 101 lines · 19 tokens per session scan A 8ecfece35e26
impact-assessor is an agent published in the GitHub repository BastiDood/dependency-wrangler (11 stars, last pushed 27d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,115 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.