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 skills/plazmodium/odin-workflow/nodejs-expressnpx skills add Plazmodium/odin-workflow --skill nodejs-expressgit clone --depth 1 https://github.com/Plazmodium/odin-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.00024 | $0.01608 |
| Opus 5 | $0.00012 | $0.00804 |
| Sonnet 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 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.
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.
- yesterday 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 3mo ago), licensed MIT. It adds 24 tokens to every session and 1,608 once invoked, about $0.0001 per session on Opus 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.