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/cbepx/talos-mcp-server/talos-mcpgit clone --depth 1 https://github.com/CBEPX/talos-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/cbepx/talos-mcp-server/talos-mcp)<a href="https://agentmods.dev/rules/cbepx/talos-mcp-server/talos-mcp"><img src="https://agentmods.dev/badge/rules/cbepx/talos-mcp-server/talos-mcp.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.00394 |
| Opus 5 | $0.00000 | $0.00197 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
talos-mcp 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 5d 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
Talos MCP Server Development Rules
You are working on the Talos MCP Server, a Model Context Protocol server for managing Talos Linux clusters.
For full architectural guidelines and detailed protocols, refer to AGENTS.md.
Project Architecture
- Core:
src/talos_mcp/core/(Client, Settings, Exceptions) - Tools:
src/talos_mcp/tools/(Modular tool implementations) - Server:
src/talos_mcp/server.py(Entry point, MCP registration) - Tests:
tests/(pytest, integration tests)
Coding Standards (Clean Code)
- Type Hints: Strict usage of
typingmodule. All functions must have return type hints. - Docstrings: Google-style docstrings for all classes and functions.
- Read-Only Safety:
- All mutating tools MUST set
is_mutation = Truein their class definition. server.pyenforces read-only mode by checking this flag.
- All mutating tools MUST set
- Error Handling:
- Use
TalosCommandErrorfor CLI failures. - Catch specific exceptions, never bare
except:.
- Use
- Logging: Use
loguru(imported aslogger). Do not use standardlogging.
Testing
- Unit Tests: Run with
make test. - Integration Tests:
make test-integration(Requires sudo/Docker). - Manual Verification:
python tests/manual_verification.py.
Versioning
- Version is defined in
src/talos_mcp/server.pyandpyproject.toml. - Keep
CHANGELOG.mdupdated.
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.
- 5d ago First seen · 36 lines · 0 tokens per session scan A d8254ef12fe0
talos-mcp is a cursor rule published in the GitHub repository CBEPX/talos-mcp-server (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 394 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.