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 skills add Plazmodium/odin-workflow --skill nodejs-fastifygit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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-fastify)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/nodejs-fastify"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/nodejs-fastify/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-fastify"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/nodejs-fastify.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.00019 | $0.01024 |
| Opus 5.5 | $0.00008 | $0.00410 |
| Sonnet 5.5 | $0.00004 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
nodejs-fastify 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js + Fastify
Overview
Fastify is a high-performance Node.js web framework focused on developer experience and low overhead. It uses JSON Schema for request/response validation and serialization.
Project Structure
src/
├── app.ts # Fastify instance + plugin registration
├── server.ts # Entry point (start server)
├── plugins/
│ ├── auth.ts # Auth decorator/plugin
│ └── database.ts # DB connection plugin
├── routes/
│ ├── auth/
│ │ ├── index.ts # Route registration
│ │ └── schema.ts # JSON schemas
│ └── users/
│ ├── index.ts
│ └── schema.ts
├── services/
│ └── user.service.ts # Business logic
├── types/
│ └── index.ts # TypeScript types
└── tests/
└── routes/
└── auth.test.ts
Core Patterns
App Setup
import Fastify from 'fastify';
const app = Fastify({
logger: true,
ajv: { customOptions: { removeAdditional: 'all' } },
});
// Register plugins
await app.register(import('./plugins/database'));
await app.register(import('./plugins/auth'));
// Register routes
await app.register(import('./routes/auth'), { prefix: '/auth' });
await app.register(import('./routes/users'), { prefix: '/users' });
export default app;
Routes with Schema Validation
import { FastifyPluginAsync } from 'fastify';
const userRoutes: FastifyPluginAsync = async (fastify) => {
fastify.get('/:id', {
schema: {
params: { type: 'object', properties: { id: { type: 'string', format: 'uuid' } }, required: ['id'] },
response: {
200: {
type: 'object',
properties: {
id: { type: 'string' },
email: { type: 'string' },
name: { type: 'string' },
},
},
},
},
preHandler: [fastify.authenticate],
handler: async (request, reply) => {
const { id } = request.params as { id: string };
const user = await fastify.userService.getById(id);
if (!user) return reply.code(404).send({ error: 'Not found' });
return user;
},
});
};
export default userRoutes;
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 · 153 lines · 19 tokens per session scan A ce0a1fafc3c7
nodejs-fastify is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 1,024 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.