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.
git clone --depth 1 https://github.com/Justdvp/claude-code-templatesWrote 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/commands/justdvp/claude-code-templates/npm-scripts)<a href="https://agentmods.dev/commands/justdvp/claude-code-templates/npm-scripts"><img src="https://agentmods.dev/badge/commands/justdvp/claude-code-templates/npm-scripts/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/commands/justdvp/claude-code-templates/npm-scripts"><img src="https://agentmods.dev/badge/commands/justdvp/claude-code-templates/npm-scripts.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.00300 |
| Opus 5.5 | $0.00000 | $0.00120 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
npm-scripts 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- npm-scripts — 100% identical, 0 lines differ
What it actually says
NPM Scripts Assistant
Help me with NPM scripts: $ARGUMENTS
Task
I'll help you work with package.json scripts by:
- Analyzing existing npm scripts in your project
- Creating new scripts or modifying existing ones
- Explaining what specific scripts do
- Suggesting improvements or optimizations
- Troubleshooting script execution issues
Process
I'll follow these steps:
- Examine your package.json file to understand current scripts
- Analyze dependencies and devDependencies for available tools
- Identify common patterns and conventions in your scripts
- Implement requested changes or create new scripts
- Provide explanations of how the scripts work
- Test scripts when possible to verify functionality
Common Script Types I Can Help With
- Build processes (webpack, rollup, esbuild, etc.)
- Development servers and hot reloading
- Testing (unit, integration, e2e)
- Linting and code formatting
- Type checking
- Deployment and CI/CD
- Database migrations
- Code generation
- Environment setup
- Pre/post hooks for git operations
Script Optimization Techniques
- Parallelizing tasks for faster execution
- Adding cross-platform compatibility
- Improving error reporting and logging
- Implementing watch modes for development
- Creating composite scripts for common workflows
- Adding appropriate exit codes for CI/CD pipelines
I'll adapt my approach based on your project's specific needs, dependencies, and build tools.
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 · 48 lines · 0 tokens per session scan A 96b6b4b6c174
npm-scripts is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 300 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-31.
Other commands, from other repositories
audit-steps
Audit one or all pipelines against layout, frontmatter, topology, and runtime-safety standards — produces a severity-classified report (SEV-0/1/2/3) with cited evidence.
delete-step
Delete a step from an existing pipeline — select pipeline, select step, perform gap analysis, optionally rewire, audit the delta, then gate on human approval before any deletion.
init-deep
Initiates a repository traversal to create localized PIPELINE-CONTEXT.md hierarchical context files.
migrate-pipeline
Migrate an existing pre-v2 per-tier pipeline (.claude/, .opencode/, .agents/codex/) into the unified data-only .superpipelines/ layout — select legacy pipeline, translate frontmatter to canonical agent defs, stage, delta-audit, gate on human approval, then atomically promote, rewrite the registry, and move the legacy…
change-models
Set, change, or audit model preferences for pipeline agents — interactive 6-mode workflow (global/workspace prefs, per-agent overrides, first-run wizard, catalog refresh).
new-pipeline
Design and scaffold a new named multi-agent pipeline with git preflight, scope selection, pre-gate audit, and entry-skill generation.