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/curiositech/some_claude_skillsWrote 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/plugins/curiositech/some_claude_skills/caching-strategies)<a href="https://agentmods.dev/plugins/curiositech/some_claude_skills/caching-strategies"><img src="https://agentmods.dev/badge/plugins/curiositech/some_claude_skills/caching-strategies.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
caching-strategies 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
{
"name": "caching-strategies",
"description": "Design multi-tier caching architectures for web applications \u2014 cache-aside vs write-through vs write-behind, TTL design, cache invalidation, Redis patterns, CDN configuration, browser caching, and stampede prevention. Use when choosing a caching pattern, designing cache invalidation strategies, implementing Redis caching, configuring Cache-Control headers, or preventing cache stampedes. Activate on \"cache invalidation\", \"cache-aside\", \"write-through\", \"TTL\", \"Redis cache\", \"CDN caching\", \"cache stampede\", \"stale data\", \"browser cache\". NOT for database query caching within an ORM, memoization of pure functions, or CPU-level caching."
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 137 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 5 lines scan A b694dfeda35d
caching-strategies is a plugin published in the GitHub repository curiositech/some_claude_skills (214 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-06.
Other plugins, from other repositories
upstash
The Upstash MCP server plus agent skills for every Upstash SDK and CLI — Redis, QStash, Workflow, Box, Blob, Ratelimit, Vector, and Search.
upstash
The Upstash MCP server plus agent skills for every Upstash SDK and CLI — Redis, QStash, Workflow, Box, Blob, Ratelimit, Vector, and Search.
api-cache-manager
Implement caching strategies with Redis, CDN, and HTTP headers.
api-rate-limiter
Implement rate limiting with token bucket, sliding window, and Redis.
redis-channel
Claude Code channel that bridges sessions to external systems over Redis Streams. Router-agnostic: pair with any router implementation that speaks the protocol.
cache-architect
Design caching strategies with Redis.