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.
npx agentmods add rules/willibrandon/netcontextserver/cligit clone --depth 1 https://github.com/willibrandon/NetContextServerWhat 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 | $0.00000 | $0.00481 |
| Opus 5 | $0.00000 | $0.00241 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
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 yesterday.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Tool Implementation Rules
This rule provides guidance for implementing the Command Line Interface (CLI) for the .NET Codebase Context Server, with specific optimizations for Claude 3.7 Sonnet integration.
AI-Assisted Development
- Use descriptive XML comments that explain the "why" behind implementation choices
- Include example usage for each command in code comments
- Structure commands into logical groups with consistent naming patterns
- Ensure each command has a clear, single responsibility
- Add CLI output examples in comments to help Claude understand expected behavior
Command Structure
- Use verb-noun pattern for all commands (e.g.,
list-projects,search-code) - Implement consistent parameter naming across similar commands
- Support both short and long option formats for all parameters
- Include help text that explains parameter relationships and constraints
- Group related commands into command sets with shared context
Error Handling
- Return structured JSON responses with error codes and descriptive messages
- Include targeted troubleshooting guidance in error messages
- Implement detailed logging with contextual information
- Add correlation IDs to associate related operations for troubleshooting
- Handle graceful shutdown for CTRL+C and other interrupts
User Experience
- Provide colorized, formatted output with clear visual hierarchy
- Implement progress indicators for long-running operations
- Support interactive mode for complex operations
- Add "did you mean?" suggestions for common command typos
- Include completion scripts for bash/zsh/PowerShell
Documentation
- Create example-driven documentation with realistic scenarios
- Document each command with purpose, parameters, examples, and limitations
- Include troubleshooting sections for common issues
- Add visual guides showing command relationships and workflows
- Provide explicit mapping between CLI commands and MCP protocol capabilities
AI Integration Features
- Add machine-readable JSON output option for all commands
- Support template-based rendering of results for custom output formats
- Include metadata in command responses to aid in AI understanding
- Add descriptive response schemas for Claude to better understand outputs
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.
- yesterday First seen · 55 lines · 481 tokens per session scan A 822dd749a481
cli is a cursor rule published in the GitHub repository willibrandon/NetContextServer (32 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 481 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-30.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.