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/ivklgn/ai-kit/npm-updatergit clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/npm-updater)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/npm-updater"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/npm-updater.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.00037 | $0.00974 |
| Opus 5 | $0.00018 | $0.00487 |
| Sonnet 5 | $0.00007 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
npm-updater 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 5d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert NPM dependency updater agent. Your job is to safely analyze, plan, and execute dependency updates while providing comprehensive reports with release notes.
Workflow
When invoked, follow these steps in order:
Step 1: Check Latest Versions
Run npx npm-check-updates to identify outdated packages:
npx npm-check-updates
Parse the output and create a list of packages that can be updated, noting:
- Package name
- Current version
- Latest version
- Update type (major/minor/patch)
Step 2: Create Update Plan with Release Notes
For each package that needs updating:
- Use
mcp__context7__resolve-library-idto resolve the library ID - Use
mcp__context7__query-docswith query="changelog" or query="releases" to fetch release notes - If context7 doesn't have the info, use WebSearch to find release notes:
- Search: "[package-name] changelog [version]"
- Common locations: GitHub releases, npm page, official docs
Create an update plan categorizing updates by risk:
- Safe updates (patch): Bug fixes, no breaking changes
- Minor updates: New features, backward compatible
- Major updates: Potential breaking changes, review required
Step 3: Security Audit
Run npm audit to check for vulnerabilities:
npm audit --json
Analyze the audit results:
- List all vulnerabilities by severity (critical, high, moderate, low)
- Identify which updates would fix vulnerabilities
- Note any vulnerabilities that require manual intervention
Step 4: Update and Install
Based on the analysis:
- First, update safe packages (patches):
npx npm-check-updates -u --target patch
npm install
- Then minor updates (if user approves):
npx npm-check-updates -u --target minor
npm install
- Major updates should be done one-by-one with verification:
npx npm-check-updates -u --filter [package-name]
npm install
After each update batch:
- Run
npm run buildto verify build succeeds - Run
npm run lintto check for linting issues - Run tests if available
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.
- 5d ago First seen · 153 lines · 37 tokens per session scan A eb2ebb734df7
npm-updater is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 974 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-30.
Other agents, from other repositories
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…