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/ccoalm/ccl-skills/nodejs-service-devnpx skills add ccoalm/ccl-skills --skill nodejs-service-devgit clone --depth 1 https://github.com/ccoalm/ccl-skillsWrote 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/ccoalm/ccl-skills/nodejs-service-dev)<a href="https://agentmods.dev/skills/ccoalm/ccl-skills/nodejs-service-dev"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-skills/nodejs-service-dev.svg" alt="Measured on agentmods" 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 | $0.00184 | $0.01626 |
| Opus 5 | $0.00092 | $0.00813 |
| Sonnet 5 | $0.00037 | $0.00325 |
| Haiku 4.5 | $0.00018 | $0.00163 |
Grade A, and why
nodejs-service-dev 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js Service Development
Skill Routing
- Use this skill for Node.js service implementation: handlers, middleware, adapters, workers, jobs, clients, runtime/toolchain mechanics, and focused tests.
- New capabilities, cross-module architecture, service redesigns, and multi-stage refactors enter
product-rd-workflow; verified repairs return here afterdefect-diagnosis. testing-strategychooses test layers, coverage policy, contract/E2E scope, and CI gates. This skill owns Node runner, mock, fixture, and command mechanics after that choice.- Standalone CLI/tooling stays here; language-stack CLI implementation must not be routed back to
terminal-cli-dev, owner of the interface contract; logs/metrics/traces toplatform-observability; cross-service timeout/retry/mTLS toplatform-service-connectivity; rollout/rollback toplatform-release-engineering. - Browser UI goes to
web-react-dev; LLM/RAG/agent-runtime behavior tollm-inference-integration. Keep language-neutral rules in their existing owner. - Architecture, service-boundary, and data-ownership decisions have no Node architecture sibling skill by decision: they run through
product-rd-workflow's architecture gate plus the relevantplatform-*owners, and this skill owns the Node-side implementation contract. Do not borrow the Go or Python architecture skill for a Node.js service. - The runtime contract here is Node.js. Bun and Deno share much of this service shape, but their runtime, package, permission, and built-in-API semantics differ and are not verified against this skill's sources: reuse the boundary and lifecycle rules, confirm every runtime-specific claim against that runtime's own documentation, and treat a deliberate migration as a
product-rd-workflowdecision rather than a drop-in swap.
Generalization Discipline
- Implement the repository in front of you; do not lift product nouns, service names, package paths, or organization-specific habits from a prior codebase into a reusable rule.
- When adding or revising durable Node.js guidance, place it deliberately. A rule that depends on Node runtime or toolchain mechanics — module resolution, TypeScript execution, event loop, streams,
worker_threads, package-manager state — stays here. Generic backend service practice belongs in the shared workflow, testing, or architecture owner; a lesson that also holds for a sibling stack updatesgo-microservice-devorpython-service-devin the same landing instead of living only here. - The duty runs inward too: a generic backend rule already landed in a sibling stack skill applies here unless Node runtime semantics make it wrong. Record the per-sibling decision —
update,unchanged, orroute-to-shared— rather than leaving the sibling unexamined.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +10 lines 96206c6babad
- 4d ago First seen · 65 lines · 184 tokens per session scan A 728ab6b5ec6a
nodejs-service-dev is a skill published in the GitHub repository ccoalm/ccl-skills (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 184 tokens to every session and 1,626 once invoked, about $0.0009 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…