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 WrongStack/WrongStack --skill node-backendgit clone --depth 1 https://github.com/WrongStack/WrongStackWrote 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/wrongstack/wrongstack/node-backend)<a href="https://agentmods.dev/skills/wrongstack/wrongstack/node-backend"><img src="https://agentmods.dev/badge/skills/wrongstack/wrongstack/node-backend/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/wrongstack/wrongstack/node-backend"><img src="https://agentmods.dev/badge/skills/wrongstack/wrongstack/node-backend.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.00052 | $0.00646 |
| Opus 5.5 | $0.00021 | $0.00258 |
| Sonnet 5.5 | $0.00010 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
node-backend 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 7d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node Backend
Selection card
- Task: Implement Node server endpoints and shutdown.
- Start: Locate the endpoint, schema, authentication boundary and caller.
- Finish: apply the acceptance checks below; report observed results and unresolved constraints.
Overview
Build and upgrade Node.js HTTP services with typed validation, lifecycle ownership and production behavior.
Checked 2026-10-09: Hono 4.13.13, Fastify 5.12.5 and NestJS 12.1.2. Latest stable Node target is 26.11.1; verify framework/plugins/adapter requirements together.
Rules
- Inspect framework lifecycle, plugin/dependency injection order and actual runtime adapter.
- Validate input and serialize public output at the route boundary; do not expose database rows or internal exceptions wholesale.
- Bound request bodies, external calls and expensive work according to application limits.
- Keep per-request auth/context isolated and authorize each operation/object.
- Make startup, readiness and graceful shutdown include owned pools/listeners/jobs.
- Verify framework error/cancellation semantics; returning an error-shaped object may still produce a success response.
Workflow
- Trace route → service → persistence/external operation and existing conventions.
- Resolve latest stable targets and supported plugins before migration.
- Implement the feature with explicit contracts and lifecycle cleanup.
- Test valid/invalid/unauthorized input, dependency failure and stop/restart.
- Run configured type/lint/tests and a production server health/user-path check.
Before returning
Route/auth/output contracts verified; startup/shutdown resources owned; framework compatibility and actual server behavior recorded.
Sources
Versioned facts checked 2026-10-09; refresh authoritative sources before new installs/upgrades. Hono, Fastify, NestJS.
Skills in scope
- node-modern — node modern contracts and verification.
- api-design — api design contracts and verification.
- database-development — implement database access, models and queries with explicit consistency, transactions and bounded results.
- authentication-sessions — implement application sign-in, sessions and identity integration with explicit account/tenant authorization.
- queues-jobs — implement reliable asynchronous jobs and message consumers with explicit delivery, retry and shutdown semantics.
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.
- 7d ago Changed 7e891d0d7762
- 8d ago First seen · 60 lines · 52 tokens per session scan A e8292ba99cd7
node-backend is a skill published in the GitHub repository WrongStack/WrongStack (380 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 646 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
latchkey
Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.
api-baas-firebase
Firebase backend-as-a-service — Firestore, Authentication, Cloud Functions v2, Storage, Hosting, Admin SDK, security rules, emulator suite.
api-baas-neon
Serverless PostgreSQL with branching, autoscaling, and edge-compatible driver.
api-auth-clerk
Clerk managed authentication - ClerkProvider, middleware, pre-built components, hooks, server-side auth, organizations, webhooks.
api-baas-supabase
Supabase backend-as-a-service — Auth, Database, Realtime, Storage, Edge Functions, RLS policies, typed client.
api-caching-strategies
Application-level caching strategies, HTTP caching, cache invalidation, and stampede prevention.