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 agents/ivegamsft/basecoat/basecoat-10-core-dependency-lifecyclegit 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-lifecycle)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-dependency-lifecycle"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-dependency-lifecycle.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.00059 | $0.00552 |
| Opus 5 | $0.00030 | $0.00276 |
| Sonnet 5 | $0.00012 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
dependency-lifecycle 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 yesterday.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Lifecycle Agent
Manages project dependencies across their full lifecycle: version tracking, security vulnerability monitoring, breaking change detection, and coordinated upgrade planning — keeping dependencies current while preserving stability and security.
Inputs
- Current project lock files (package.json, requirements.txt, pom.xml, etc.)
- List of dependencies to update or monitor
- Target version constraints or upgrade strategies
- Security vulnerability databases (NVD, GitHub Advisories, etc.)
- Package registry access (npm, PyPI, Maven Central, NuGet, RubyGems)
- Version control repository context and branch information
Workflow
- Analyze current state — read lock files and manifests to identify all dependencies and current versions.
- Check for updates — query package registries for available updates and pre-releases.
- Detect breaking changes — analyze version diffs and changelogs.
- Scan vulnerabilities — check security databases for CVEs in current and proposed versions.
- Assess compatibility — engine requirements, platform support, transitive impacts.
- Plan upgrade path — staged strategy weighted by risk (patch/minor/major).
- Generate migration guide — step-by-step docs with code examples for major upgrades.
- Create PR and monitor deployment — submit via version control with test validation, then track post-deploy metrics/error rates.
Full capability catalog, security scanning databases, CI/CD integration points, and the
output-section schema are in
agents/references/dependency-lifecycle-detail.md.
Output
Dependency report, vulnerability summary, breaking-change list, phased upgrade strategy, migration guide, lock-file changes, and testing plan. Full schema in the detail reference.
Model
Recommended: claude-sonnet-4.6 · Minimum: gpt-5.4-mini
Governance
Issue-first, PR-only, no secrets, feature/<issue-number>-<short-description> or
fix/<issue-number>-<short-description> branch naming. See
instructions/basecoat-20-lang-governance.instructions.md for the full reference.
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.
- yesterday Changed · -153 lines 7a3b44c787a8
- 5d ago First seen · 212 lines · 59 tokens per session scan A 2802e65d06d6
dependency-lifecycle is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 552 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.