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/Azure-Samples/mcp-agent-langchainjsWrote 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/azure-samples/mcp-agent-langchainjs/update-npm-packages)<a href="https://agentmods.dev/commands/azure-samples/mcp-agent-langchainjs/update-npm-packages"><img src="https://agentmods.dev/badge/commands/azure-samples/mcp-agent-langchainjs/update-npm-packages/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/azure-samples/mcp-agent-langchainjs/update-npm-packages"><img src="https://agentmods.dev/badge/commands/azure-samples/mcp-agent-langchainjs/update-npm-packages.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00389 |
| Opus 5.5 | $0.00000 | $0.00156 |
| Sonnet 5.5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
update-npm-packages 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.
What it actually says
Context
This is an npm workspaces monorepo. The root package.json defines "workspaces": ["packages/*"]. The minimum supported Node.js version is declared in engines.node of the root package.json.
Rules
@types/nodemust NEVER be updated to a new major version unless the minimum Node.js version inengines.nodechanges. Minor and patch updates are fine.- Do not update packages to versions that drop support for the project's minimum Node.js version.
- When a package has a major update, check its changelog or release notes for breaking changes before updating.
- If a major update introduces breaking changes that require code modifications, make those changes.
- If you're unsure whether a breaking change is safe, ask the user before proceeding.
Task
- Run
npm outdatedat the workspace root to get the full list of outdated packages across all workspaces. - Identify and categorize updates:
- Patch/minor updates: safe to apply in batch.
- Major updates: require individual review for breaking changes.
- Apply all patch and minor updates first by running
npm updateat the workspace root. - Run
npm outdatedagain to see remaining major updates. - For each major update (respecting the rules above):
a. Check the package's changelog/release notes for breaking changes.
b. If safe, update the version range in the relevant
package.jsonfile(s) and runnpm install. c. If code changes are needed, apply them. d. If unsure, ask the user before proceeding. - After all updates, run
npm run buildto verify the project still compiles. - Run
npm run lintto check for any new lint issues introduced by the updates. - Report a summary of all changes made.
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 First seen · 29 lines · 0 tokens per session scan A d29aebedcd58
update-npm-packages is a command published in the GitHub repository Azure-Samples/mcp-agent-langchainjs (204 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 389 tokens. 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-10-29.
Other commands, from other repositories
setup-gemini.en
Command "setup-gemini.en" from minicoohei/ai-agent-camp, covering gemini api setup, step 0: check setup progress, what you'll do in this session, readiness check and step 1: open google ai studio in the browser.
validate-pipeline
Validate data pipeline configuration and data quality rules.
ml-run-review
Review a machine learning training run or experiment configuration for soundness, reproducibility, and evaluation rigor.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.