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 agentmods add skills/emasoft/claude-plugins-validation/cpv-batch-caching-optimizenpx skills add Emasoft/claude-plugins-validation --skill cpv-batch-caching-optimizegit clone --depth 1 https://github.com/Emasoft/claude-plugins-validationWrote 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/emasoft/claude-plugins-validation/cpv-batch-caching-optimize)<a href="https://agentmods.dev/skills/emasoft/claude-plugins-validation/cpv-batch-caching-optimize"><img src="https://agentmods.dev/badge/skills/emasoft/claude-plugins-validation/cpv-batch-caching-optimize.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 | $0.00114 | $0.01197 |
| Opus 5 | $0.00057 | $0.00598 |
| Sonnet 5 | $0.00023 | $0.00239 |
| Haiku 4.5 | $0.00011 | $0.00120 |
Grade A, and why
cpv-batch-caching-optimize 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpv-batch-caching-optimize
Overview
Parallel cache-fix skill. Runs Phase 1 (Audit) → Phase 2 (Fix) → Phase 3 (Re-validate) of the cpv-cache-optimizer-agent workflow across every plugin in the user's input spec. Phase 4 (Broader refactor) is deliberately skipped in batch mode because every Phase 4 step requires interactive per-step approval and that doesn't compose with a parallel dispatch.
Same input grammar and dispatch shape as
cpv-batch-validate. The
orchestrator body lives in this plugin's
commands/cpv-batch-caching-optimize.md slash-command file.
Prerequisites
claude-plugins-validationplugin installed (provides thecpv-cache-optimizer-agent, the universal input resolver, and the cache validator + fix recipes).- For URL inputs:
giton PATH and network access togithub.com. - Write access to every plugin's tree — this skill mutates source
files in place (it's the fix variant of
cpv-batch-caching-audit). - Each plugin's tree should be a clean working tree (committed or
stashed) before the run so the per-plugin agents can produce
inspectable
fix(cache-CA-NN): ...commits.
Inputs
See the cpv-batch-validate input table — every shape is supported identically.
Instructions
- Confirm the user wants to APPLY fixes (this skill mutates plugin
files). If they want a read-only snapshot, route to
cpv-batch-caching-audit. - Invoke the slash command body:
/cpv-batch-caching-optimize <user's spec> [--max-parallel N] - Each agent runs Phase 1 → Phase 2 → Phase 3 on its assigned plugin (Phase 4 skipped in batch).
- The user gets the final status table + a one-line summary
(
DONE: plugins=N clean=X fixed=Y partial=Z failed=W). - For Phase 4 (broader refactor — extracting shared cache headers,
restructuring agent contexts), run the
cpv-cache-optimizer-agenton that single plugin interactively (it performs Phase 4 with the required per-step approval that does not compose with a parallel batch).
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.
- 3d ago First seen · 109 lines · 114 tokens per session scan A 201f6de908c5
cpv-batch-caching-optimize is a skill published in the GitHub repository Emasoft/claude-plugins-validation (4 stars, last pushed 5d ago), licensed MIT. It adds 114 tokens to every session and 1,197 once invoked, about $0.0006 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
redis-js
Work with the Upstash Redis JavaScript/TypeScript SDK for serverless Redis operations. Use for caching, session storage, rate limiting, leaderboards, full-text search (querying, filtering, aggregating with @upstash/redis search extension), and all Redis data structures. Supports automatic serialization/deserialization…
walkeros-using-store-cache
Use when adding read-through caching to a walkerOS store, memoizing a slow API/Sheets backing, composing multi-tier cache chains, or deduplicating concurrent store reads. Covers recipes, TTL choice, error policy, and observability counters.
database-patterns
Use when designing PostgreSQL + Redis data models, indexes, caching strategies, JSONB usage, tiered storage, or cache consistency contracts.
redis-search
Redis Search guidance covering FT.CREATE schema design, field type selection (TEXT, TAG, NUMERIC, GEO, GEOSHAPE, VECTOR, JSON path), DIALECT 2 query syntax, FT.SEARCH / FT.AGGREGATE / FT.HYBRID command selection, vector similarity with HNSW or FLAT, hybrid retrieval combining lexical and vector ranking, RAG pipelines…
redis-connections
Redis client and connection guidance covering connection pooling, multiplexing, pipelining, client-side caching with RESP3, avoiding slow commands (KEYS, SMEMBERS, HGETALL), and tuning socket timeouts. Use when configuring a Redis client (redis-py, Jedis, Lettuce, NRedisStack), batching commands for throughput…
iris-development
Iris is Redis's umbrella for AI-focused products. Use this skill when integrating with the Iris Redis Agent Memory (RAM) data plane on Redis Cloud — recording session events for an AI agent, creating or searching long-term memories, configuring a memory store, or tuning background memory promotion. Code examples use…