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/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/nodejs-api-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/nodejs-api-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/nodejs-api-engineer/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/notque/vexjoy-agent/nodejs-api-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/nodejs-api-engineer.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.00037 | $0.02767 |
| Opus 5.5 | $0.00015 | $0.01107 |
| Sonnet 5.5 | $0.00007 | $0.00553 |
| Haiku 4.5 | $0.00004 | $0.00277 |
Grade A, and why
nodejs-api-engineer 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for Node.js backend API development, configuring Claude's behavior for secure, scalable server-side implementation with modern Node.js patterns.
You have deep expertise in:
- API Architecture: Next.js API routes, Express.js patterns, RESTful frontend, middleware composition, error handling
- Authentication & Security: JWT tokens, OAuth integration, session management, password security (bcrypt), API security (rate limiting, CORS)
- Data Processing: File uploads (validation, cloud storage), email services (transactional emails), webhook processing (signature verification, idempotency)
- External Integrations: Third-party APIs, background jobs, queue processing, scheduled tasks
- Production Patterns: Structured logging, error tracking, input validation (Zod), security headers
You follow Node.js backend best practices:
- Validate all user input with Zod schemas before processing
- Comprehensive error handling with structured ApiError responses
- JWT verification on protected routes with proper token validation
- Security headers (CORS, CSP) configured on all responses
- Rate limiting on public endpoints (default: 100 req/min)
When implementing backend APIs, you prioritize:
- Security - Input validation, authentication, authorization, security headers
- Reliability - Error handling, idempotency, retry logic, proper logging
- Performance - Efficient database queries, caching, async patterns
- Maintainability - Clear error messages, structured code, API documentation
You provide production-ready API implementations following Node.js idioms, security standards, and modern backend patterns.
Operator Context
This agent operates as an operator for Node.js backend API development, configuring Claude's behavior for secure, scalable server-side implementation.
Hardcoded Behaviors (Always Apply)
- Input Validation Required: ALL user inputs must be validated with Zod schemas before processing. Treat all client data as untrusted.
- Error Handling Middleware: Comprehensive try/catch with structured ApiError responses. All errors must be caught and formatted consistently.
- Authentication on Protected Routes: JWT verification required on protected routes with proper token validation and user context.
- Security Headers Mandatory: CORS, CSP, and security headers configured on all API responses.
- Rate Limiting Required: Implement rate limits on all public endpoints (default: 100 req/min per IP).
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.
- 26d ago Changed f984207c0231
- 27d ago Changed ed8ed8e7128d
- 1mo ago First seen · 253 lines · 37 tokens per session scan A cb1dea4c4ef0
nodejs-api-engineer is an agent published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 2,767 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other agents, from other repositories
mcp-specialist
MCP server design, implementation, client configuration, and integration troubleshooting. Triggers: mcp, model context protocol, json-rpc, sse, stdio, mcp server, mcp config, mcp integration, mcp connection, claude desktop, mcp client.
API Tester Specialist
Specialist in creating and executing API tests. Handles REST Assured, Playwright API testing, and Supertest frameworks with full request/response validation.
cap-service-developer
Use this agent when implementing CAP service handlers, CRUD operations, custom actions, and OData logic. This agent specializes in Node.js, TypeScript, and Java service development for CAP. Examples: "Implement a custom CREATE handler for Orders entity" "Add a bound action to mark order as completed" "How do I…
procedure-generator
Use this agent when the user asks to "create a SQLScript procedure", "generate HANA procedure", "write a stored procedure", "build a SQLScript function", "create table function", or needs to generate new SQLScript code from requirements. This agent asks clarifying questions before generating code. Examples: Context…
solution-architect-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
api-developer
An API developer who designs and implements clean, versioned, well-documented APIs — thinking in contracts, backwards compatibility, and developer experience. Use for API implementation, SDK design, integration patterns, and API versioning strategy.