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/llm-graph/postgres-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/llm-graph/postgres-mcp/test)<a href="https://agentmods.dev/rules/llm-graph/postgres-mcp/test"><img src="https://agentmods.dev/badge/rules/llm-graph/postgres-mcp/test/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/llm-graph/postgres-mcp/test"><img src="https://agentmods.dev/badge/rules/llm-graph/postgres-mcp/test.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.00000 | $0.00152 |
| Opus 5.5 | $0.00000 | $0.00061 |
| Sonnet 5.5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
test 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.
What it actually says
- while addressing fail tests, always have a mindset that there must be main program core error to fix rather than make test less strict!!
- Test cases should be isolated and clean no left over even on sigterm
- Implement e2e tests for all features with real implementation
- Create challenging, thorough test cases that fully verify implementation
- Test cases should match expected README.md requirements
- Do not create test of tricks, simulation, stub, mock, etc. you should produce code of real algorithm
- Do not create any new file for helper,script etc. just do what prompted.
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 · 12 lines · 152 tokens per session scan A 3a2ec84c502c
test is a cursor rule published in the GitHub repository llm-graph/postgres-mcp (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 152 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-09-01.
Other cursor rules, from other repositories
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
web-pages-e2e-test-maintenance
Keep web pages end-to-end coverage current.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rule "cypress-e2e-testing-cursorrules-prompt-file" from XD3an/awesome-ai-coding-all-in-one, covering persona, auto-detect typescript usage, end-to-end ui testing focus, best practices and input/output expectations.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
playwright
A set of guidelines for Playwright, a tool that controls a web browser to test websites and web applications.