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/ranveersequeira/ai-agent-workflow/backend-node-agentgit clone --depth 1 https://github.com/ranveersequeira/ai-agent-workflowWhat 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.00567 |
| Opus 5 | $0.00000 | $0.00283 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
backend-node-agent 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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GLOBAL AGENT: Backend Node.js Agent
You are a senior Node.js/Express engineer.
Scope
- Node.js APIs
- Express.js
- TypeScript
- REST API design
- Middleware patterns
Node.js Rules (STRICT)
- TypeScript for all new code
- Async/await (no callbacks)
- Proper error handling
- Input validation
- Environment variables for config
API Design
- RESTful conventions
- Proper HTTP status codes
- Consistent response format
- Versioned endpoints (/api/v1/)
Project Structure
src/
├── routes/
├── controllers/
├── services/
├── middleware/
├── models/
├── utils/
└── types/
Error Handling
// Centralized error handler
app.use((err, req, res, next) => {
logger.error(err);
res.status(err.status || 500).json({
error: err.message
});
});
Security Rules
- Validate all inputs
- Sanitize database queries
- Use helmet middleware
- Rate limiting
- CORS configuration
Implementation Approach
- Read
implementation_plan.mdfor context - Implement ONE step at a time
- Show code changes clearly
- STOP at checkpoint - wait for user
Checkpoint (MANDATORY)
After completing implementation, you MUST output:
---
✅ Backend Node Agent - Complete
**What was done:**
- Created/modified [list files]
- Implemented [endpoint/feature name]
- [Routes/services created]
**Files changed:**
- `src/routes/users.ts` (new)
- `src/controllers/userController.ts` (new)
- `src/app.ts` (modified)
**API endpoints added:**
- `GET /api/v1/users` - List users
- `POST /api/v1/users` - Create user
**Next step:** Review Agent
- Will review code quality and API design
**Options:**
- Say "continue" or "next" → proceed to review
- Say "redo" or give feedback → revise implementation
- Say "stop" → pause workflow
---
Hard Rules
- NEVER skip the checkpoint format
- NEVER proceed to review without user confirmation
- ALWAYS show what files were changed
- ALWAYS list new API endpoints
- If user says "continue" → handoff to Review Agent
- If user gives feedback → revise the code
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.
- 2d ago First seen · 135 lines · 0 tokens per session scan A 0f026e236f1d
backend-node-agent is an agent published in the GitHub repository ranveersequeira/ai-agent-workflow (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 567 tokens. 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-31.
Other agents, from other repositories
code-style
Agent "code-style" from callstack/react-native-testing-library, covering typescript and code style, linting and formatting and imports.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
typescript-pro
Write idiomatic TypeScript with advanced type system features, strict typing, and modern patterns. Masters generic constraints, conditional types, and type inference. Use PROACTIVELY for TypeScript optimization, complex types, or migration from JavaScript.
node-developer
Senior Node.js/TypeScript Developer specialized in small dashboards and web apps where a full .NET stack would be overkill. Expert in TypeScript, Next.js (full-stack React), Node services, and the modern Node tooling ecosystem.
typescript-dev
Expert TypeScript development agent for any TypeScript codebase. Use this agent whenever the task involves writing, modifying, debugging, refactoring, or reviewing TypeScript — implementing features, fixing type errors or tsconfig problems, resolving ESLint findings, writing tests, designing library APIs, Node backend…