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 skills/justanesta/claude-code-resources/webdev-javascript-fundamentalsnpx skills add justanesta/claude-code-resources --skill webdev-javascript-fundamentalsgit clone --depth 1 https://github.com/justanesta/claude-code-resourcesWhat 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.00038 | $0.02201 |
| Opus 5 | $0.00019 | $0.01100 |
| Sonnet 5 | $0.00008 | $0.00440 |
| Haiku 4.5 | $0.00004 | $0.00220 |
Grade A, and why
webdev-javascript-fundamentals scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url, options); How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JavaScript Fundamentals for Web Development
Core Principles
- Modern ES2024+ syntax — Use
const/let, arrow functions, optional chaining, nullish coalescing, and structured clone as defaults - Immutability by default — Prefer
const, non-mutating array methods (toSorted,toReversed,toSpliced), andstructuredClonefor deep copies - Async-first patterns — Use
async/awaitover raw Promises; handle errors at appropriate boundaries with structured error types - Declarative array transformations — Chain
map,filter,reduce,flatMapinstead of imperative loops - Explicit module boundaries — Use ES modules with named exports; keep module APIs small and focused
Modern Variable Declarations and Destructuring
Use const for all bindings that are not reassigned. Use let only when reassignment is necessary. Never use var.
// Destructuring objects with defaults and renaming
const { name, age = 0, address: { city } = {} } = user;
// Destructuring arrays with skip and rest
const [first, , third, ...remaining] = items;
// Nested destructuring in function parameters
function createOrder({ product: { id, name }, quantity = 1, discount = 0 }) {
const total = calculatePrice(id, quantity) * (1 - discount);
return { id: crypto.randomUUID(), product: name, quantity, total };
}
// Nullish coalescing and optional chaining
const displayName = user?.profile?.displayName ?? user?.name ?? "Anonymous";
const theme = settings?.theme ?? "system";
// Structured clone for deep copies (no prototype or function copying)
const snapshot = structuredClone(state);
See async-patterns.md for: advanced destructuring in async contexts and parameter handling.
Async/Await Patterns
Always use async/await for asynchronous code. Handle errors at the appropriate boundary rather than on every call.
// Parallel execution with Promise.all
async function loadDashboard(userId) {
const [profile, orders, notifications] = await Promise.all([
fetchProfile(userId),
fetchOrders(userId),
fetchNotifications(userId),
]);
return { profile, orders, notifications };
}
// Error boundary with structured error handling
async function fetchWithRetry(url, options = {}, retries = 3) {
for (let attempt = 1; attempt <= retries; attempt++) {
try {
const response = await fetch(url, options);
if (!response.ok) throw new HttpError(response.status, await response.text());
return await response.json();
} catch (error) {
if (attempt === retries) throw error;
await new Promise((r) => setTimeout(r, 2 ** attempt * 100));
}
}
}
// AbortController for cancellation
async function searchWithTimeout(query, timeoutMs = 5000) {
const controller = new AbortController();
const timeoutId = setTimeout(() => controller.abort(), timeoutMs);
try {
return await fetch(`/api/search?q=${encodeURIComponent(query)}`, {
signal: controller.signal,
});
} finally {
clearTimeout(timeoutId);
}
}
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 251 lines · 38 tokens per session scan A 87110611ffea
webdev-javascript-fundamentals is a skill published in the GitHub repository justanesta/claude-code-resources (2 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 2,201 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.