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/giantswarm/mcp-prometheusWrote 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/giantswarm/mcp-prometheus/architecture)<a href="https://agentmods.dev/rules/giantswarm/mcp-prometheus/architecture"><img src="https://agentmods.dev/badge/rules/giantswarm/mcp-prometheus/architecture/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/giantswarm/mcp-prometheus/architecture"><img src="https://agentmods.dev/badge/rules/giantswarm/mcp-prometheus/architecture.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.00332 | $0.00332 |
| Opus 5.5 | $0.00133 | $0.00133 |
| Sonnet 5.5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
architecture 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.
This is a copy
92% identical to architecture — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Architecture Principles
This document outlines the fundamental architectural principles and patterns for the mcp-prometheus codebase. Adherence to these guidelines is mandatory to maintain a clean, decoupled, and testable system.
1. Testing Standards
- Minimum Coverage: All new code MUST achieve at least 80% unit test coverage.
- No Flaky Tests: Tests MUST be deterministic. Do not use
time.Sleepor other mechanisms that can lead to race conditions. Use dependency injection for things like clocks or timers to make code testable.
2. Go Development & Style
- Formatting: Before every commit, run:
goimports -w . go fmt ./... - Dependencies: Before adding a new dependency with
go get, search the web to find its latest stable version. This is a must! - Error Handling: Wrap errors with
fmt.Errorf("context: %w", err)to preserve context. - File Size: Keep files focused and under 500 lines. Refactor larger files.
3. Documentation
- Packages: Every package MUST have a
doc.gofile explaining its purpose. - Exported Members: Every exported function, type, and variable MUST have a GoDoc comment.
- Project Docs: New features or significant changes require updates to the relevant documents in the
docs/directory.
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 · 37 lines · 332 tokens per session scan A f4e424ecba90
architecture is a cursor rule published in the GitHub repository giantswarm/mcp-prometheus (11 stars, last pushed today), licensed Apache-2.0. It adds 332 tokens to every session, about $0.0013 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to architecture, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
toc-readme
When updating README.md, the table of contents should contain only the second-level headings below it.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
validate-design-early
Ask for design approval before implementing 100+ lines.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.