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 mduongvandinh/ai-best-practices-skills --skill nodejs-best-practicesgit clone --depth 1 https://github.com/mduongvandinh/ai-best-practices-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/mduongvandinh/ai-best-practices-skills/nodejs-best-practices)<a href="https://agentmods.dev/skills/mduongvandinh/ai-best-practices-skills/nodejs-best-practices"><img src="https://agentmods.dev/badge/skills/mduongvandinh/ai-best-practices-skills/nodejs-best-practices/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/mduongvandinh/ai-best-practices-skills/nodejs-best-practices"><img src="https://agentmods.dev/badge/skills/mduongvandinh/ai-best-practices-skills/nodejs-best-practices.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.00000 | $0.01635 |
| Opus 5 | $0.00000 | $0.00817 |
| Sonnet 5 | $0.00000 | $0.00327 |
| Haiku 4.5 | $0.00000 | $0.00163 |
Grade A, and why
nodejs-best-practices 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 12d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
21 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.
- ide-adapters/cursor.mdc 2.4 KB
- knowledge/00_Tong_Quan.md 3.0 KB
- knowledge/01_Cau_Truc_Du_An.md 11 KB
- knowledge/02_Error_Handling_Async.md 14 KB
- knowledge/03_REST_API_Middleware.md 8.5 KB
- knowledge/04_Authentication_Security.md 12 KB
- knowledge/05_Database.md 9.9 KB
- knowledge/06_Validation.md 10 KB
- knowledge/07_Testing.md 9.7 KB
- knowledge/08_Performance_Memory.md 9.9 KB
- knowledge/09_Logging_Monitoring.md 15 KB
- knowledge/10_Configuration.md 15 KB
- knowledge/11_Dependency_Management.md 12 KB
- knowledge/12_TypeScript.md 18 KB
- knowledge/13_Async_Event_Loop.md 22 KB
- knowledge/14_Caching.md 17 KB
- knowledge/15_WebSocket.md 15 KB
- knowledge/16_Deployment.md 15 KB
- knowledge/17_File_Stream.md 20 KB
- nodejs-best-practices.skill 3.1 KB
- README.md 6.8 KB
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.
- 12d ago First seen · 152 lines · 0 tokens per session scan A 64ab21794d31
nodejs-best-practices is a skill published in the GitHub repository mduongvandinh/ai-best-practices-skills (18 stars, last pushed 6mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,635 tokens. 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-30.
Other skills, from other repositories
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
cocoreview
CocoReview — structured code review with six-severity findings vocabulary, progressive disclosure architecture, and universal anti-pattern baseline. Invoked via $review [file] [--complexity] [--security] [--architecture] [--language ].
lsp-inspect
Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…
lsp-dead-code
Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing for dead code, cleaning up APIs, or checking which exports are safe to remove.
lsp-impact
Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it. Use when refactoring, deleting, or changing the signature of any function, type, or method. Also accepts a file path to surface all exported-symbol impact in one shot.
code-review
Review code changes for concrete defects.