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 danygiguere/audit-skills --skill audit-cachinggit clone --depth 1 https://github.com/danygiguere/audit-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/skills/danygiguere/audit-skills/audit-caching)<a href="https://agentmods.dev/skills/danygiguere/audit-skills/audit-caching"><img src="https://agentmods.dev/badge/skills/danygiguere/audit-skills/audit-caching/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/danygiguere/audit-skills/audit-caching"><img src="https://agentmods.dev/badge/skills/danygiguere/audit-skills/audit-caching.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.00045 | $0.00117 |
| Opus 5 | $0.00023 | $0.00059 |
| Sonnet 5 | $0.00009 | $0.00023 |
| Haiku 4.5 | $0.00005 | $0.00012 |
Grade A, and why
audit-caching 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 11d 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
Read ../audit/references/operability/caching.md and apply its checklist to the code the
user specified (or the current diff if none was given). Verify each candidate
with ../audit/references/methodology/verify.md before reporting. Report findings with severity and
file:line references.
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.
- 11d ago First seen · 10 lines · 45 tokens per session scan A 31a8f756a2ad
audit-caching is a skill published in the GitHub repository danygiguere/audit-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 117 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
qdrant-monitoring-debugging
Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries are slow', 'latency spike', or 'search was fast now it's slow'. Also use when performance degrades without obvious config changes.
huawei-cloud-mrs-redis-meta-check
A checker for Redis cluster metadata files named nodes-*.conf. Redis is an in-memory data store, and a cluster uses these files to record nodes, slots, and master-replica relationships.
performance
Use when optimizing application performance — caching strategies, eager loading, query optimization, Redis patterns, or background job design.
auditing-datastore-exposure-and-abuse
Audit in-memory and cache datastores such as Redis and memcached for exposure and command abuse: an instance reachable without authentication, a request that composes datastore commands from untrusted input, or server-side scripting and module or config commands that reach code execution or a file write. Covers…
performance-caching-rate-limits
Use this capability for performance optimization, load tests, k6/JMeter/Locust plans, caching, Redis, CDN, Cache-Control, invalidation, rate limiting, quotas, token bucket, sliding window, 429 behavior, abuse protection, and cost-based throttling.
perf-engineering
A guide to finding and fixing slow code, excessive memory use, slow startup, repeated database queries, and inefficient caching.