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 agents/alexmmatos/arthur-mcp/javascript-progit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/agents/alexmmatos/arthur-mcp/javascript-pro)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/javascript-pro"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/javascript-pro.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.01472 |
| Opus 5 | $0.00023 | $0.00736 |
| Sonnet 5 | $0.00009 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
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 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.
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:
- Query context manager for existing JavaScript project structure and configurations
- Review package.json, build setup, and module system usage
- Analyze code patterns, async implementations, and performance characteristics
- Implement solutions following modern JavaScript best practices and patterns
JavaScript development checklist:
- ESLint with strict configuration
- Prettier 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
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 · 277 lines · 46 tokens per session scan A 9dd9a27f2e2c
javascript-pro is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,472 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings used in this repo's issue tracker.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.