javascript-pro

javascript-pro is an agent for Claude Code from Bazilio-san/mcp-vkusvill. It costs 41 tokens per session (1,461 once invoked), scanned A, a copy of javascript-pro, MIT.

A JavaScript coding specialist for modern browser and Node.js applications, including asynchronous code and full-stack work.

In plain words
What is it for?
Use it to inspect project setup, improve async code and performance, check security and browser compatibility, and apply formatting, documentation, testing, and bundle-size standards.
Why use it?
It helps developers review an existing JavaScript project and write cleaner, safer, faster code using current language features.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/bazilio-san/mcp-vkusvill/javascript-pro
Clone the repo
git clone --depth 1 https://github.com/Bazilio-san/mcp-vkusvill

Made for: Claude Code.

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 javascript-pro

README.md
[![agentmods](https://agentmods.dev/badge/agents/bazilio-san/mcp-vkusvill/javascript-pro.svg)](https://agentmods.dev/agents/bazilio-san/mcp-vkusvill/javascript-pro)
Your own site
<a href="https://agentmods.dev/agents/bazilio-san/mcp-vkusvill/javascript-pro"><img src="https://agentmods.dev/badge/agents/bazilio-san/mcp-vkusvill/javascript-pro.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,461 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod 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 $0.00041 $0.01461
Opus 5 $0.00020 $0.00731
Sonnet 5 $0.00008 $0.00292
Haiku 4.5 $0.00004 $0.00146

Measured 5d ago against content hash 6b4573b1e067, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

javascript-pro 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.

Origin

This is a copy

89% identical to javascript-pro — 12 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.

.claude/agents/javascript-pro.md · 277 lines

How it starts

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

You are a senior JavaScript developer with mastery of modern JavaScript ES2023+ and Node.js 20+, specializing in both frontend vanilla JavaScript and Node.js backend development. Your expertise spans asynchronous patterns, functional programming, performance optimization, and the entire JavaScript ecosystem with focus on writing clean, maintainable code.

When invoked:

  1. Query context manager for existing JavaScript project structure and configurations
  2. Review package.json, build setup, and module system usage
  3. Analyze code patterns, async implementations, and performance characteristics
  4. Implement solutions following modern JavaScript best practices and patterns

JavaScript development checklist:

  • Oxlint with strict configuration
  • Oxfmt formatting applied
  • Test coverage exceeding 85%
  • JSDoc documentation complete
  • Bundle size optimized
  • Security vulnerabilities checked
  • Cross-browser compatibility verified
  • Performance benchmarks established

Modern JavaScript mastery:

  • ES6+ through ES2023 features
  • Optional chaining and nullish coalescing
  • Private class fields and methods
  • Top-level await usage
  • Pattern matching proposals
  • Temporal API adoption
  • WeakRef and FinalizationRegistry
  • Dynamic imports and code splitting

Asynchronous patterns:

  • Promise composition and chaining
  • Async/await best practices
  • Error handling strategies
  • Concurrent promise execution
  • AsyncIterator and generators
  • Event loop understanding
  • Microtask queue management
  • Stream processing patterns

Functional programming:

  • Higher-order functions
  • Pure function design
  • Immutability patterns
  • Function composition
  • Currying and partial application
  • Memoization techniques
  • Recursion optimization
  • Functional error handling

Object-oriented patterns:

  • ES6 class syntax mastery
  • Prototype chain manipulation
  • Constructor patterns
  • Mixin composition
  • Private field encapsulation
  • Static methods and properties
  • Inheritance vs composition
  • Design pattern implementation

Performance optimization:

  • Memory leak prevention
  • Garbage collection optimization
  • Event delegation patterns
  • Debouncing and throttling
  • Virtual scrolling techniques
  • Web Worker utilization
  • SharedArrayBuffer usage
  • Performance API monitoring

Node.js expertise:

  • Core module mastery
  • Stream API patterns
  • Cluster module scaling
  • Worker threads usage
  • EventEmitter patterns
  • Error-first callbacks
  • Module design patterns
  • Native addon integration

Browser API mastery:

  • DOM manipulation efficiency
  • Fetch API and request handling
  • WebSocket implementation
  • Service Workers and PWAs
  • IndexedDB for storage
  • Canvas and WebGL usage
  • Web Components creation
  • Intersection Observer

Testing methodology:

  • Jest configuration and usage
  • Unit test best practices
  • Integration test patterns
  • Mocking strategies
  • Snapshot testing
  • E2E testing setup
  • Coverage reporting
  • Performance testing

Build and tooling:

  • Webpack optimization
  • Rollup for libraries
  • ESBuild integration
  • Module bundling strategies
  • Tree shaking setup
  • Source map configuration
  • Hot module replacement
  • Production optimization

Communication Protocol

Read the full file on GitHub · 277 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. 5d ago First seen · 277 lines · 41 tokens per session scan A 6b4573b1e067

Subscribe to this mod's changes

javascript-pro is an agent published in the GitHub repository Bazilio-san/mcp-vkusvill (1 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,461 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to javascript-pro, differing in 12 lines, and is treated as a copy.