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 skills add saaspegasus/django-skills --skill upgrade-js-depsgit clone --depth 1 https://github.com/saaspegasus/django-skillsWrote 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/skills/saaspegasus/django-skills/upgrade-js-deps)<a href="https://agentmods.dev/skills/saaspegasus/django-skills/upgrade-js-deps"><img src="https://agentmods.dev/badge/skills/saaspegasus/django-skills/upgrade-js-deps/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/skills/saaspegasus/django-skills/upgrade-js-deps"><img src="https://agentmods.dev/badge/skills/saaspegasus/django-skills/upgrade-js-deps.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.00027 | $0.00373 |
| Opus 5 | $0.00014 | $0.00187 |
| Sonnet 5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
upgrade-js-deps 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 10d 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.
This is a copy
100% identical to upgrade-js-deps — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Your task
Upgrade all JavaScript dependencies and verify nothing is broken.
Step 1: Check for available upgrades
Run npx npm-check-updates to see what upgrades are available. Review the output and
present the list to the user.
Step 2: Update package.json
Run npx npm-check-updates -u to update package.json with the new versions.
Step 3: Install updated dependencies
Run make npm-install to install the upgraded dependencies and update package-lock.json.
Step 4: Run post-upgrade checks
Run these checks sequentially, stopping if any step fails:
- TypeScript type checking: Run
make npm-type-checkand report any new type errors. - Build: Run
make npm-buildto verify the production build still works. - Tests: Run
make testto verify the test suite still passes.
Step 5: Summarize and commit
Summarize what was done:
- Which packages were upgraded (notable version changes)
- Whether any type errors were introduced
- Whether the build succeeded
- Whether all tests passed
- Any issues that need manual attention
If there were failures, present the issues and ask how the user wants to proceed.
If everything passed, ask the user if they'd like to commit the changes. If yes, commit
using the /commit skill.
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.
- 10d ago First seen · 51 lines · 27 tokens per session scan A 101f1d285226
upgrade-js-deps is a skill published in the GitHub repository saaspegasus/django-skills (30 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 373 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to upgrade-js-deps, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.