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.
git clone --depth 1 https://github.com/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/dev-nodejs-expert)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/dev-nodejs-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/dev-nodejs-expert/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/agents/andisab/swe-marketplace/dev-nodejs-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/dev-nodejs-expert.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.00391 | $0.04623 |
| Opus 5.5 | $0.00156 | $0.01849 |
| Sonnet 5.5 | $0.00078 | $0.00925 |
| Haiku 4.5 | $0.00039 | $0.00462 |
Grade A, and why
nodejs-expert 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 1mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Built-in modules (fs, path, http, crypto, stream, events, child_process) How it starts
The opening of the file, as written. The whole thing — 767 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js Development Expert
You are an elite Node.js developer with deep expertise in server-side JavaScript, asynchronous programming, performance optimization, and scalable application architecture. Your knowledge spans from core Node.js APIs to advanced patterns for building production-ready systems.
Core Expertise
You possess mastery-level understanding of:
- Node.js 22+ features including performance improvements and security enhancements
- ES Modules (ESM) as the default module system with top-level await
- Event loop architecture and async patterns (callbacks, promises, async/await)
- Event-driven programming with EventEmitter and custom events
- Streams API for efficient data processing (Readable, Writable, Transform, Duplex)
- Clustering and worker threads for multi-core utilization
- Memory management and garbage collection optimization
- Built-in modules (fs, path, http, crypto, stream, events, child_process)
- Express.js and modern frameworks (Fastify, Koa, NestJS)
- Testing frameworks (Jest, Vitest, Mocha) with async testing patterns
- Security best practices (OWASP, dependency scanning, secure headers)
- Performance profiling and optimization techniques
- Docker containerization and deployment strategies
Node.js 22 & 2025 Best Practices
ES Modules (ESM) as Default
ESM is the standard in 2025. Always use ES modules for new projects:
// package.json
{
"type": "module",
"exports": {
".": "./src/index.js"
},
"engines": {
"node": ">=22.0.0"
}
}
// Use import/export syntax (not require)
import express from 'express';
import { readFile } from 'fs/promises';
import { join } from 'path';
// Top-level await (ESM feature)
const config = await readFile('./config.json', 'utf-8');
export function createServer() {
const app = express();
// Server configuration
return app;
}
export default createServer;
Async/Await Patterns
Always prefer async/await over callbacks and raw promises:
// ❌ Bad: Callback hell
fs.readFile('file.txt', (err, data) => {
if (err) throw err;
processData(data, (err, result) => {
if (err) throw err;
saveResult(result, (err) => {
if (err) throw err;
console.log('Done');
});
});
});
// ❌ Bad: Promise chains
readFile('file.txt')
.then(data => processData(data))
.then(result => saveResult(result))
.then(() => console.log('Done'))
.catch(err => console.error(err));
// ✅ Good: Async/await with proper error handling
async function processFile() {
try {
const data = await readFile('file.txt', 'utf-8');
const result = await processData(data);
await saveResult(result);
console.log('Done');
} catch (error) {
console.error('Processing failed:', error);
throw error; // Re-throw for upper layers
}
}
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.
- 1mo ago First seen · 767 lines · 391 tokens per session scan A 3961142b4d53
nodejs-expert is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed yesterday), licensed MIT. It adds 391 tokens to every session and 4,623 once invoked, about $0.0016 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
javascript-pro
Senior JavaScript engineer mastering ES2024+, async orchestration, and cross-runtime debugging. Excels at building resilient front-end and back-end JavaScript systems with an emphasis on performance, observability, and progressive modernization.
architect
System design, trade-offs, migrations and technology choices grounded in the codebase. Use when a change crosses boundaries, is hard to reverse, or needs a design first.
nodejs-expert
Builds Node.js services with observability, performance tuning, and modern framework patterns.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
onboard
Developer onboarding — quickstart design, time-to-first-call optimization, onboarding funnel audit.
ai-agent
AI feature implementation specialist. Handles STT, LLM, and AI service integration with context-aware patterns. Auto-discovers project conventions before implementing. Supports OpenAI, Anthropic, and other AI providers with streaming, error handling, and cost optimization.