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 skills add 1999AZZAR/project-guardian-mcp-server --skill guardian-cachegit clone --depth 1 https://github.com/1999AZZAR/project-guardian-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/skills/1999azzar/project-guardian-mcp-server/guardian-cache)<a href="https://agentmods.dev/skills/1999azzar/project-guardian-mcp-server/guardian-cache"><img src="https://agentmods.dev/badge/skills/1999azzar/project-guardian-mcp-server/guardian-cache/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/skills/1999azzar/project-guardian-mcp-server/guardian-cache"><img src="https://agentmods.dev/badge/skills/1999azzar/project-guardian-mcp-server/guardian-cache.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.00041 | $0.00376 |
| Opus 5 | $0.00020 | $0.00188 |
| Sonnet 5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
guardian-cache 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 9d 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
Guardian Cache
Standardized Redis-backed caching for agents.
Prerequisites
- Binary: Python 3.9+ must be available on the host.
- Credentials:
REDIS_URLenvironment variable (e.g.,redis://localhost:6379/0).
Setup
- Install dependencies with
python3 -m pip install -r skills/guardian-cache/requirements.txt. - Export
REDIS_URL; use.env.exampleonly as a configuration reference.
Core Workflows
1. Store and Retrieve
- Store:
printf '%s' "$VALUE" | python3 $WORKSPACE/skills/guardian-cache/scripts/cache_manager.py set mema:cache:<name> --stdin --ttl 3600 - Fetch:
python3 $WORKSPACE/skills/guardian-cache/scripts/cache_manager.py get mema:cache:<name>
2. Search & Maintenance
- Scan:
python3 $WORKSPACE/skills/guardian-cache/scripts/cache_manager.py scan [pattern] - Ping:
python3 $WORKSPACE/skills/guardian-cache/scripts/cache_manager.py ping
Prefer --stdin for values so secrets and private data do not appear in process listings or shell history. Explicit TTL values must be positive.
Key Naming Convention
Strictly enforce the mema: prefix:
mema:context:*– Session state.mema:cache:*– Volatile data.mema:state:*– Persistent state.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 35 lines · 41 tokens per session scan A 6fc38b20fa5d
guardian-cache is a skill published in the GitHub repository 1999AZZAR/project-guardian-mcp-server (3 stars, last pushed 9d ago), licensed MIT. It adds 41 tokens to every session and 376 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
brainctl
Unified agent memory CLI — read, write, search, and maintain the shared memory spine (brain.db). Use for persistent cross-session memory, knowledge graph, event logging, decisions, affect tracking, and consolidation.
sfcc-caching
Unified caching playbook for SFCC (page cache vs custom cache vs service response cache). Use this when improving performance, reducing external calls, designing cache keys/TTLs, or debugging stale cache behavior.
adk-redis
Redis backends for Google's Agent Development Kit (ADK). Use this skill when the user wants to back an ADK agent with Redis: persistent sessions and long-term memory via Redis Agent Memory Server, RAG search tools over a RedisVL index (vector / hybrid / range / text / SQL), MCP toolsets for RedisVL or Agent Memory…
orchardcore-ai-memory-elasticsearch
Skill for indexing CrestApps Orchard Core AI Memory with Elasticsearch. Covers memory field mappings, dense vectors, k-nearest-neighbor retrieval, default query fields, user isolation, and Elasticsearch operations. Use this skill when requests mention AI Memory Elasticsearch, AIMemoryElasticsearchIndexProfileHandler…
redis
Use Redis correctly as a cache, queue, rate limiter, and ephemeral store — pick the right data structure, caching pattern, eviction policy, and atomicity model. Use when adding caching, designing a key schema, choosing cache-aside vs write-through, setting TTLs/eviction, building a rate limiter or queue, debugging low…
slm-cache
KV cache for repeated reads — call slmcacheget(key) first; on a miss do the expensive operation then slmcacheset(key, value, ttlseconds) to store it; on a hit use the returned value directly; always fail-open (hit:false on any error, never raises); saves tokens when the same file, query result, or tool output is read…