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/ChangooLee/mcp-kr-legislationWrote 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/changoolee/mcp-kr-legislation/30-cache-management)<a href="https://agentmods.dev/rules/changoolee/mcp-kr-legislation/30-cache-management"><img src="https://agentmods.dev/badge/rules/changoolee/mcp-kr-legislation/30-cache-management.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.00424 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
30-cache-management 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 7d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 7d ago First seen · 48 lines · 0 tokens per session scan A 31504f735117
30-cache-management is a cursor rule published in the GitHub repository ChangooLee/mcp-kr-legislation (9 stars, last pushed 4mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 424 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
redis
This guide provides definitive, actionable best practices for using Redis effectively, focusing on data modeling, performance, security, and cluster-aware client usage to build robust and scalable applications.
cache
A set of guidance for using a cache, a temporary data store that keeps frequently needed information available for faster access. It describes cache operations and a shared data center for access to stored data.
full-test-with-db-redis
Run full tests with Docker db and redis.
redis_rate_limiting
Complete guide for implementing Redis-based rate limiting with authentication troubleshooting and FastAPI integration.
nestjs-6-database-performance
USE WHEN working with databases, implementing repositories, optimizing queries, caching, or performance tuning.
caching-management
A set of rules for storing frequently used data in memory and in JSON files, with expiry times and a size limit.