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 CodeInfinity1/Stram --skill node-debugginggit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/node-debugging)<a href="https://agentmods.dev/skills/codeinfinity1/stram/node-debugging"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/node-debugging/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/codeinfinity1/stram/node-debugging"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/node-debugging.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.00027 | $0.00417 |
| Opus 5.5 | $0.00011 | $0.00167 |
| Sonnet 5.5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
node-debugging 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.
What it actually says
Node Debugging
Purpose
Diagnose Node.js and frontend/backend JavaScript problems with repository-native commands and browser evidence. Inspector or DevTools workflows are used only through configured native tools or approved shell commands.
When To Use
Use for Node runtime errors, npm scripts, bundler issues, frontend bugs, server logs, inspector workflows, and browser/Node integration problems.
Inputs And Evidence
- Error output, package scripts, lockfiles, source files, browser state, and reproduction steps.
- Node/npm versions and test/build commands.
Tool Map
read_filesearch_workspacerun_shell_commandbrowser_live_openbrowser_live_observesystematic-debugging
Workflow
- Inspect package scripts and runtime versions.
- Reproduce with the smallest relevant command.
- Trace stack frames to source and tests.
- Use browser tools for UI-visible bugs.
- Patch narrowly and run targeted verification.
- Report version/tooling blockers explicitly.
Native Implementation Boundaries
- Use repo commands through Stram shell/browser tools.
- Do not import external reference node-inspector scripts.
- Do not install packages without user approval.
Safety And Approval
- Network/package installs require approval.
- Do not kill or restart services without checking user impact.
- Avoid logging secrets from env or browser storage.
Verification
- Test/build/dev-server output or browser observation should prove the result.
- If a server remains running, track and stop/report it as appropriate.
- Note local-only vs CI verification.
Failure Modes
- Fixing minified/generated output instead of source.
- Ignoring lockfile/package-manager conventions.
- Treating browser symptoms as pure frontend without checking API responses.
References
- Shortlist item:
node-debugging. - Upstream inspiration: external reference node debugging references only.
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 · 67 lines · 27 tokens per session scan A 7e5cc8c6898d
node-debugging is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 417 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-03.
Other skills, from other repositories
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.
footprint
Use when building flowchart pipelines with footprintjs — stage functions, decider branches, selectors, subflows, loops, narrative traces, recorders, redaction, contracts, and LLM-ready output. Also use when someone asks how footprint.js works or wants to understand the library.
rb:runtime
Integrating the Tidewave runtime for live Rails introspection: code exec, SQL queries, model inspection, log retrieval against a running server.
rb:state-audit
Auditing Rails request-scoped state hygiene: CurrentAttributes, sessions, caching policies, Redis usage, request-lifecycle leaks between calls.
a-unslop-code
Finds what makes source code read as AI-written and points you at the parts that actually ship bugs. Sorts every tell into three buckets and fixes them in that order: bugs (swallowed errors, a made-up API, a left-in "rest of the code" stub), substance (tutorial-shaped boilerplate, over-engineering, code that ignores…
error-handling-design-review
Use this skill when error taxonomy, retries, timeouts, fallback, or recovery design needs an evidence-bounded review before implementation; triggers include error handling design review, failure-path review, and recovery readiness review.