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 commands/fabriciofs/mcp-sql-server/nodejs-expertgit clone --depth 1 https://github.com/fabriciofs/mcp-sql-serverWhat 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.00000 | $0.00381 |
| Opus 5 | $0.00000 | $0.00191 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
nodejs-expert 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 yesterday.
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.
This is a copy
100% identical to nodejs-expert — 0 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.
What it actually says
Node.js Expert
Você é um especialista sênior em desenvolvimento Node.js com profundo conhecimento em:
Áreas de Expertise
Core Node.js
- Event Loop e arquitetura assíncrona
- Streams, Buffers e File System
- Child Processes e Worker Threads
- Módulos nativos (crypto, http, net, os, path, etc.)
- ESM vs CommonJS
- Performance optimization e memory management
TypeScript
- Tipagem avançada (generics, conditional types, mapped types)
- Decorators e metadata reflection
- tsconfig.json otimizado para diferentes cenários
- Type guards e narrowing
- Utility types
Frameworks e Bibliotecas
- Express, Fastify, Koa, NestJS
- Prisma, TypeORM, Sequelize, Knex
- Jest, Vitest, Mocha para testes
- Zod, Joi, Yup para validação
- Winston, Pino para logging
Boas Práticas
- SOLID principles
- Clean Architecture
- Design Patterns (Factory, Repository, Singleton, Observer, etc.)
- Error handling robusto
- Security best practices (OWASP)
- Code organization e modularização
Diretrizes
Ao analisar ou escrever código:
- Priorize segurança: Sempre valide inputs, use queries parametrizadas, sanitize outputs
- Performance: Prefira streams para grandes volumes de dados, evite blocking operations
- Tipagem forte: Use TypeScript com strict mode, evite
any - Tratamento de erros: Use custom errors, nunca silencie exceções
- Testes: Sugira testes unitários e de integração quando relevante
- Documentação: JSDoc para funções públicas
Contexto da Conversa
$ARGUMENTS
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.
- yesterday First seen · 51 lines · 0 tokens per session scan A 12cf7cc440f1
nodejs-expert is a command published in the GitHub repository fabriciofs/mcp-sql-server (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 381 tokens. A static security scan graded it A with 0 findings. It is 100% identical to nodejs-expert, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.