Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Plazmodium/odin-workflownpx agentmods add skills/plazmodium/odin-workflow/nodejs-expressWrote 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/skills/plazmodium/odin-workflow/nodejs-express)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/nodejs-express"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/nodejs-express/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/skills/plazmodium/odin-workflow/nodejs-express"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/nodejs-express.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.00024 | $0.01608 |
| Opus 5.5 | $0.00010 | $0.00643 |
| Sonnet 5.5 | $0.00005 | $0.00322 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
nodejs-express 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 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.
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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js + Express Development
Overview
Express.js is a minimal, flexible Node.js web application framework providing robust features for building web and mobile applications.
Project Structure
src/
├── index.ts # Entry point
├── app.ts # Express app setup
├── routes/
│ ├── index.ts # Route aggregator
│ ├── auth.routes.ts # Auth endpoints
│ └── user.routes.ts # User endpoints
├── controllers/
│ ├── auth.controller.ts
│ └── user.controller.ts
├── services/
│ ├── auth.service.ts
│ └── user.service.ts
├── middleware/
│ ├── auth.middleware.ts
│ ├── error.middleware.ts
│ └── validation.middleware.ts
├── models/ # Database models
├── utils/
│ └── asyncHandler.ts # Async error wrapper
└── types/
└── index.ts # TypeScript types
Core Patterns
App Setup
// src/app.ts
import express from 'express';
import cors from 'cors';
import helmet from 'helmet';
import { errorHandler } from './middleware/error.middleware';
import routes from './routes';
const app = express();
// Security middleware
app.use(helmet());
app.use(cors());
// Body parsing
app.use(express.json());
app.use(express.urlencoded({ extended: true }));
// Routes
app.use('/api/v1', routes);
// Error handling (must be last)
app.use(errorHandler);
export default app;
Async Handler Pattern
// src/utils/asyncHandler.ts
import { Request, Response, NextFunction } from 'express';
type AsyncFunction = (
req: Request,
res: Response,
next: NextFunction
) => Promise<any>;
export const asyncHandler = (fn: AsyncFunction) => {
return (req: Request, res: Response, next: NextFunction) => {
Promise.resolve(fn(req, res, next)).catch(next);
};
};
Controller Pattern
// src/controllers/user.controller.ts
import { Request, Response } from 'express';
import { asyncHandler } from '../utils/asyncHandler';
import * as userService from '../services/user.service';
export const getUsers = asyncHandler(async (req: Request, res: Response) => {
const users = await userService.findAll();
res.json({ success: true, data: users });
});
export const getUserById = asyncHandler(async (req: Request, res: Response) => {
const user = await userService.findById(req.params.id);
if (!user) {
res.status(404).json({ success: false, error: 'User not found' });
return;
}
res.json({ success: true, data: user });
});
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 · 278 lines · 24 tokens per session scan A 5588b8b33821
nodejs-express is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,608 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-09-01.
Other skills, from other repositories
nornweave-api
Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…
user-usecases
Database of real user use cases for APIbase platform. Contains detailed examples of how specific APIs are onboarded, wrapped, and served to AI agents. Use this skill when you need to reference real integration examples, explain the APIbase onboarding process, or design new API wrappers based on proven patterns.
spotify-exhaustive-feature-sweep
Exhaustive feature sweep across Spotify domains — enumerate all endpoints into quantity-first tool proposals with quota flags and batched GitHub logging.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.