Borrowing it
Nothing to install: this file belongs to shyamsridhar123/Skills-Registry-CLI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shyamsridhar123/Skills-Registry-CLI/main/.github/skills/npm-cli-builder/SKILL.mdgit clone --depth 1 https://github.com/shyamsridhar123/Skills-Registry-CLIWrote 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/shyamsridhar123/skills-registry-cli/npm-cli-builder)<a href="https://agentmods.dev/skills/shyamsridhar123/skills-registry-cli/npm-cli-builder"><img src="https://agentmods.dev/badge/skills/shyamsridhar123/skills-registry-cli/npm-cli-builder/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/shyamsridhar123/skills-registry-cli/npm-cli-builder"><img src="https://agentmods.dev/badge/skills/shyamsridhar123/skills-registry-cli/npm-cli-builder.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.00037 | $0.01083 |
| Opus 5 | $0.00018 | $0.00541 |
| Sonnet 5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
npm-cli-builder 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 10d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NPM CLI Builder Skill
This skill provides guidance for building npm CLI tools with proper structure, argument parsing, and npm publishing.
CLI Project Structure
<cli-name>/
├── package.json
├── bin/
│ └── <cli-name>.js # Entry point with shebang
├── src/
│ ├── index.js # Main exports
│ ├── commands/ # Command implementations
│ │ ├── install.js
│ │ ├── list.js
│ │ └── validate.js
│ ├── lib/ # Core logic
│ │ ├── registry.js
│ │ ├── installer.js
│ │ └── validator.js
│ └── utils/ # Utilities
│ ├── logger.js
│ └── config.js
├── README.md
└── LICENSE
Package.json Configuration
{
"name": "<cli-name>",
"version": "1.0.0",
"description": "CLI tool description",
"type": "module",
"bin": {
"<cli-name>": "./bin/<cli-name>.js"
},
"main": "./src/index.js",
"engines": {
"node": ">=18.0.0"
},
"files": [
"bin",
"src"
],
"scripts": {
"start": "node bin/<cli-name>.js",
"lint": "eslint .",
"test": "node --test"
},
"keywords": ["cli", "tool"],
"license": "MIT",
"dependencies": {
"commander": "^12.0.0",
"chalk": "^5.3.0",
"ora": "^8.0.0"
}
}
CLI Entry Point Template
bin/<cli-name>.js:
#!/usr/bin/env node
import { program } from 'commander';
import { installCommand } from '../src/commands/install.js';
import { listCommand } from '../src/commands/list.js';
import { validateCommand } from '../src/commands/validate.js';
program
.name('<cli-name>')
.description('CLI tool description')
.version('1.0.0');
program
.command('install')
.description('Install skills from a repository')
.argument('<repo>', 'GitHub repository (owner/repo)')
.option('-s, --skill <name>', 'Install specific skill')
.option('-a, --all', 'Install all skills')
.action(installCommand);
program
.command('list')
.description('List installed skills')
.option('-j, --json', 'Output as JSON')
.action(listCommand);
program
.command('validate')
.description('Validate installed skills')
.argument('[skill]', 'Specific skill to validate')
.action(validateCommand);
program.parse();
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.
- 10d ago First seen · 161 lines · 37 tokens per session scan A ece8c5283571
npm-cli-builder is a skill published in the GitHub repository shyamsridhar123/Skills-Registry-CLI (2 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 1,083 once invoked, about $0.0002 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
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
dcg
Destructive Command Guard - High-performance Rust hook for Claude Code that blocks dangerous commands before execution. SIMD-accelerated, modular pack system, whitelist-first architecture. Essential safety layer for agent workflows.
go
This skill should be used when the user works with Go files (.go), asks about "error handling", "interfaces", "goroutines", "channels", "packages", or discusses Go idioms and concurrency. Provides patterns for error handling, interface design, concurrency, and package organization.
java
This skill should be used when the user works with Java files (.java), asks about "records", "sealed classes", "Optional", "streams", "composition over inheritance", or discusses modern Java patterns and API design. Provides patterns for type system usage, error handling, immutability, and concurrency.