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/samisouabni/exoscale-mcp/cursorrulesgit clone --depth 1 https://github.com/samisouabni/exoscale-mcpWrote 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/samisouabni/exoscale-mcp/cursorrules)<a href="https://agentmods.dev/rules/samisouabni/exoscale-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/samisouabni/exoscale-mcp/cursorrules.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.00125 | $0.00125 |
| Opus 5 | $0.00063 | $0.00063 |
| Sonnet 5 | $0.00025 | $0.00025 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
cursorrules 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 2d 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
Exoscale MCP Server
This is a TypeScript MCP server. For detailed context, see:
.kiro/steering/project-context.md— full project overview.kiro/steering/coding-conventions.md— patterns and styleARCHITECTURE.md— system designCONTRIBUTING.md— how to add tools and tests
Key patterns:
- Tools use Zod v4 + action discriminator
- safetyGate() required for all mutations
- Read-only mode ON by default
- Tests: createToolCaller() + mock fetch
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.
- 2d ago First seen · 14 lines · 125 tokens per session scan A 8439666f4a0b
cursorrules is a cursor rule published in the GitHub repository samisouabni/exoscale-mcp (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 125 tokens to every session, about $0.0006 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-31.
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.