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/arjshiv/localutils-mcp-serverWrote 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/arjshiv/localutils-mcp-server/package)<a href="https://agentmods.dev/rules/arjshiv/localutils-mcp-server/package"><img src="https://agentmods.dev/badge/rules/arjshiv/localutils-mcp-server/package/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/rules/arjshiv/localutils-mcp-server/package"><img src="https://agentmods.dev/badge/rules/arjshiv/localutils-mcp-server/package.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.00002 | $0.00255 |
| Opus 5.5 | $0.00001 | $0.00102 |
| Sonnet 5.5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
package 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
Package Management Standards
Dependencies
- Keep dependencies up to date
- Use exact versions for critical dependencies
- Separate dev dependencies properly
- Document dependency purposes
- Audit dependencies regularly
Scripts
- Include standard npm scripts:
- build
- test
- start
- dev
- lint
- Use consistent script naming
- Document custom scripts
- Keep scripts focused and simple
Version Management
- Follow semantic versioning
- Update version numbers appropriately
- Document version changes
- Test before version bumps
- Tag releases properly
Security
- Regular security audits
- Fix vulnerabilities promptly
- Use trusted packages only
- Keep lockfiles up to date
- Review package permissions
Configuration
- Use appropriate Node version
- Set correct package type
- Configure access properly
- Set up proper bin entries
- Include necessary files only
Publishing
- Test before publishing
- Update documentation
- Check package contents
- Verify license compliance
- Use proper registry settings
Maintenance
- Regular dependency updates
- Remove unused dependencies
- Keep scripts maintained
- Update engines field
- Review package size
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 · 59 lines · 2 tokens per session scan A f13e75d9ce39
package is a cursor rule published in the GitHub repository arjshiv/localutils-mcp-server (2 stars, last pushed 9mo ago), licensed MIT. It adds 2 tokens to every session and 255 once invoked, about $0.0000 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 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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).