upgrade-jquery

upgrade-jquery is a skill for Claude Code, Codex from Phaedra-Solutions/cursor-rules. It costs 118 tokens per session (1,234 once invoked), scanned A, original, MIT.

A guided process for upgrading jQuery, a JavaScript library commonly used to add browser interactions, while checking the plugins and pages that depend on it.

In plain words
What is it for?
Use it to move older jQuery versions to newer releases, update compatible plugins and jQuery UI, fix migration warnings, and check browser behavior.
Why use it?
It helps find outdated APIs and multiple bundled copies that can cause browser errors after a jQuery upgrade.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to move older jQuery versions to newer releases, update compatible plugins and jQuery UI, fix migration warnings, and check browser behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/phaedra-solutions/cursor-rules/upgrade-jquery
Install

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.

Any agent
npx skills add Phaedra-Solutions/cursor-rules --skill upgrade-jquery
Clone the repo
git clone --depth 1 https://github.com/Phaedra-Solutions/cursor-rules

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for upgrade-jquery

README.md
[![agentmods](https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-jquery/github.svg)](https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-jquery)
Your own site
<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-jquery"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-jquery/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.

agentmods 80×15 button for upgrade-jquery

Your own site · 80×15
<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-jquery"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-jquery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,234 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00118 $0.01234
Opus 5.5 $0.00047 $0.00494
Sonnet 5.5 $0.00024 $0.00247
Haiku 4.5 $0.00012 $0.00123

Measured 3d ago against content hash 6b0d827209b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

upgrade-jquery 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 3d 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.

skills/upgrade-jquery/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Upgrade jQuery

When to use

  • The project loads jQuery below 3.5.0 (vulnerable) or below 3.7.1, or the user wants jQuery 4.
  • legacy/jquery applies.

Before you start

  • Find every copy: package.json/bower.json, vendored files, CDN script tags, WordPress or CMS-bundled jQuery, and libraries that bundle their own. List plugins and jQuery UI with versions, and check each plugin's supported jQuery range.
  • Browser support: jQuery 4 drops IE 10 and older, Edge Legacy, iOS < 11, Firefox < 65 and the Android Browser. Confirm with the user before targeting 4.
  • Working tree clean; new branch; browser tests (Playwright or Cypress) for pages with jQuery behavior. Add them first if missing.

Steps

  1. Baseline: run the browser tests and click through key pages with the console open; record existing errors.
  2. Hop to 3.7.1 (from 1.x/2.x, this is the big hop):
    • load [email protected] plus jquery-migrate@3 (development build) right after it;
    • exercise every page; Migrate logs JQMIGRATE: warnings for deprecated and removed APIs;
    • fix each warning, for example: .size() → .length, .bind/.unbind/.delegate → .on/.off, $(document).ready variants, .andSelf() → .addBack(), $.parseJSON → JSON.parse, jQuery.event.props, self-closing tag handling changed by the 3.5.0 htmlPrefilter fix ($('<div/>') is fine, '<div/><span/>' strings aren't expanded);
    • upgrade jQuery UI to 1.13.2+ and plugins to versions that support 3.x; replace unmaintained plugins.
  3. Remove jQuery Migrate once no warnings remain, run the tests, and ship 3.7.1 as its own change.
  4. Hop to 4.x (if the user agreed):
    • load jquery@4 plus jquery-migrate@4 in development;
    • replace removed utilities with native code: $.trim → String.prototype.trim, $.isArray → Array.isArray, $.parseJSON → JSON.parse, $.now → Date.now, $.isFunction → typeof fn === 'function', $.type, $.isNumeric, $.isWindow, $.camelCase, $.nodeName;
    • check code that relied on JSON → JSONP auto-promotion, on push/sort/splice on jQuery objects, or on the old focus/blur event order;
    • if the slim build is used, replace Deferreds/Callbacks with native Promises;
    • consider Trusted Types (require-trusted-types-for 'script') now that jQuery 4 supports them.
  5. Remove jQuery Migrate, run everything again, and ship.
  6. Load jQuery from your build or a pinned CDN URL with integrity/crossorigin; remove other copies.
  7. Show the diff and results at each hop; commit only when asked (git-commit skill).

Read the full file on GitHub · 60 lines

Changes

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.

  1. 3d ago First seen · 60 lines · 118 tokens per session scan A 6b0d827209b7

Subscribe to this mod's changes

upgrade-jquery is a skill published in the GitHub repository Phaedra-Solutions/cursor-rules (4 stars, last pushed 2d ago), licensed MIT. It adds 118 tokens to every session and 1,234 once invoked, about $0.0005 per session on Opus 5.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-11-01.

Related

Other skills, from other repositories

grok-cli

Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and…

scarletkc/agents · 66 tokens

documentation

Use when the user asks to install or maintain a documentation index, keep CLAUDE.md or AGENTS.md inventories synchronized with files, add document metadata, classify documentation, or apply documentation-only setup to a repository.

jrenaldi79/harness-engineering · 45 tokens

talk-like-scarletkc

A writing guide that makes text sound like the developer scarletkc, including posts, comments, technical opinions, project documents, and translations.

scarletkc/agents · 118 tokens

product-writing

Write, edit, or review UI copy, CLI messages, help text, code comments, and technical documentation covering product behavior, errors, status, setup, compatibility, or technical results.

scarletkc/agents · 40 tokens

marketing-copy

Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be…

scarletkc/agents · 121 tokens

scoped-change

Judgment rules for locating the correct boundary of a requested change: staying inert outside it while completing every required site inside it. Use when scope is ambiguous, a diff touches neighboring surfaces, required dependent edits are unclear, or a proposed compatibility layer, migration, fallback, flag…

scarletkc/agents · 69 tokens