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/astrogirlnim/SkyFiMCPWrote 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/rules/astrogirlnim/skyfimcp/npm-package-check)<a href="https://agentmods.dev/rules/astrogirlnim/skyfimcp/npm-package-check"><img src="https://agentmods.dev/badge/rules/astrogirlnim/skyfimcp/npm-package-check.svg" alt="Measured on agentmods" 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.00444 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
npm-package-check 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 7d 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
NPM Package Check
// Description: Best practices for checking and installing NPM packages before use // Recommended Globs: **/*.{js,jsx,ts,tsx}, **/package.json
Overview
Ensure all required NPM packages are properly installed before use to prevent runtime errors.
Package Check Process
- Before requiring any npm package, check package.json dependencies
- If package exists in dependencies:
- Output: "✓ {package_name} is already installed"
- If package NOT found:
- Output terminal command:
npm install {package_name}
- Output terminal command:
Example Implementation
const fs = require('fs');
const path = require('path');
function checkPackage(packageName) {
try {
const packageJson = JSON.parse(
fs.readFileSync(path.join(process.cwd(), 'package.json'), 'utf8')
);
const deps = {
...packageJson.dependencies,
...packageJson.devDependencies
};
if (deps[packageName]) {
console.log(`✓ ${packageName} is already installed`);
return true;
} else {
console.log(`Installing ${packageName}...`);
console.log(`Run: npm install ${packageName}`);
return false;
}
} catch (error) {
console.error('Error reading package.json:', error);
return false;
}
}
Usage Example
// Before importing a package
if (checkPackage('express')) {
const express = require('express');
// Use express...
} else {
console.error('Please install express first');
process.exit(1);
}
Best Practices
- Always check packages before requiring them
- Handle missing package.json gracefully
- Consider both dependencies and devDependencies
- Provide clear installation instructions
- Exit gracefully if required packages are missing
Common Patterns
- Pre-startup dependency check
- Dynamic package loading
- Development tooling setup
- Build process validation
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.
- 7d ago First seen · 75 lines · 444 tokens per session scan A adb44cfcc006
npm-package-check is a cursor rule published in the GitHub repository astrogirlnim/SkyFiMCP (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 444 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.