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/sparesparrow/mcp-project-orchestrator/sharedgit clone --depth 1 https://github.com/sparesparrow/mcp-project-orchestratorWrote 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/sparesparrow/mcp-project-orchestrator/shared)<a href="https://agentmods.dev/rules/sparesparrow/mcp-project-orchestrator/shared"><img src="https://agentmods.dev/badge/rules/sparesparrow/mcp-project-orchestrator/shared.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 | $0.00009 | $0.00349 |
| Opus 5 | $0.00005 | $0.00175 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
shared 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 3d 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
OpenSSL Development Guidelines
Environment Context
- Platform: Linux x86_64
- Python: 3.11.0 (CPython)
- User: developer
- Home: /home/developer
- CI Environment: false
General Development Rules
Code Quality Standards
- Documentation: All functions, classes, and modules must have comprehensive docstrings following PEP 257 conventions
- Type Hints: Use type hints for all function parameters and return values
- Error Handling: Implement robust error handling with meaningful error messages
- Testing: Maintain high test coverage using pytest
- Linting: Code must pass Ruff linting checks
OpenSSL-Specific Guidelines
Cryptographic Best Practices
- Constant-Time Operations: Always use constant-time implementations for cryptographic operations
- Memory Management: Properly zero out sensitive memory after use
- Random Number Generation: Use cryptographically secure random number generators
- Key Management: Follow proper key generation, storage, and disposal practices
Security Considerations
- Input Validation: Validate all inputs, especially from external sources
- Buffer Overflows: Always check buffer bounds before operations
- Side-Channel Attacks: Be aware of timing and power analysis attacks
- FIPS Compliance: Ensure code meets FIPS 140-2 requirements when applicable
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.
- 3d ago First seen · 43 lines · 9 tokens per session scan A ccbf971e7e96
shared is a cursor rule published in the GitHub repository sparesparrow/mcp-project-orchestrator (17 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 349 once invoked, about $0.0000 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-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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.