Borrowing it
Nothing to install: this file belongs to jd-solanki/airig. 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/jd-solanki/airig/main/.ai/skills/node-cli/SKILL.mdgit clone --depth 1 https://github.com/jd-solanki/airigWrote 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/jd-solanki/airig/node-cli)<a href="https://agentmods.dev/skills/jd-solanki/airig/node-cli"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/node-cli/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/jd-solanki/airig/node-cli"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/node-cli.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.00059 | $0.01534 |
| Opus 5.5 | $0.00024 | $0.00614 |
| Sonnet 5.5 | $0.00012 | $0.00307 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
node-cli 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node CLI
src structure
src/
├── index.ts # Entry point — wires Commander, calls updateNotifier
├── update-notifier.d.ts # Type shim for update-notifier package
├── commands/ # One file per CLI command
│ ├── add.ts
│ └── remove.ts
├── lib/ # Pure domain logic, no Commander concerns
│ ├── github.ts # single-file feature → stays flat
│ ├── linker.ts
│ └── push/ # 2+ files → grouped into a feature folder, prefix dropped
│ ├── index.ts # barrel: re-exports the feature's public surface
│ ├── workflow.ts
│ └── validation.ts
└── utils/ # Generic helpers — mix flat files and nested groups freely
├── format.ts # flat single-purpose helper
└── fs/ # related helpers grouped under one folder
├── read.ts
└── write.ts
tests/ # Mirrors src/ structure, one test file per module
├── add.test.ts
└── linker.test.ts
conventions:
commands/— each file exports a singleCommandinstance; all CLI concerns (prompts, flags, output) live herelib/— framework-agnostic helpers imported by commands; keep them testable in isolation- Directories don't have to be flat. Keep a feature flat by default, and group it into a folder only once it owns 2+ files — a folder holding one file is just noise. When you group, the folder already names the feature, so drop the redundant prefix from filenames (
lib/push/workflow.ts, notlib/push/push-workflow.ts), and usedir/index.tsas the feature's public surface (a barrel re-exporting what commands import, or, for a provider-style seam, the interface/contract itself). Commands import the folder, not its internals:import { planPush } from '../lib/push/index.js', so each feature's internal file split can change without touching call sites.
Entry point structure
#!/usr/bin/env node
import { Command } from 'commander'
import updateNotifier from 'update-notifier'
import packageJson from '../package.json' with { type: 'json' }
// Call before parseAsync — notify() defers display to process exit so it
// never interleaves with command output.
updateNotifier({ pkg: packageJson }).notify()
const program = new Command('your-cli')
.description('...')
.version(packageJson.version)
program.addCommand(fooCommand)
await program.parseAsync()
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 · 156 lines · 59 tokens per session scan A f6518a796af6
node-cli is a skill published in the GitHub repository jd-solanki/airig (2 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 1,534 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
adapter-express
Mount tRPC as Express middleware with createExpressMiddleware() from @trpc/server/adapters/express. Access Express req/res in createContext via CreateExpressContextOptions. Mount at a path prefix like app.use('/trpc', ...). Avoid global express.json() conflicting with tRPC body parsing for FormData.
trpc-router
Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
nestjs-expert
Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating…
chat-sdk
Build multi-platform chat bots with Chat SDK (chat npm package). Use when developers want to (1) Build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, (2) Use Chat SDK to handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI…
azure-web-pubsub-ts
Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me...