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/catalystbyzoho/claude-plugin/catalyst-cachenpx skills add catalystbyzoho/claude-plugin --skill catalyst-cachegit clone --depth 1 https://github.com/catalystbyzoho/claude-pluginWhat 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.00053 | $0.00458 |
| Opus 5 | $0.00026 | $0.00229 |
| Sonnet 5 | $0.00011 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
catalyst-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 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
How It Works
Before any MCP call, establish context once per session via the workspace readiness gate:
../catalyst-basics/references/preflight.md. It resolves and reconciles the org/project soCatalystbyZoho_List_All_Segmentstargets the right project.
- Get Segment ID — Use MCP (
CatalystbyZoho_List_All_Segments) if available; otherwise retrieve it from the console or.catalystrc. - Load
references/cache-basics.md— for SDK operations, TTL limits (48 hr max), and thesegment.delete()/segment.update()gotchas. - String values only — All cache values are strings. Always
JSON.stringifybeforeputandJSON.parseafterget. - TTL behavior —
segment.update(key, value)without an expiry argument resets the TTL to 48 hours (the max), not the key's original TTL. Always pass the TTL explicitly (in hours) to preserve it:segment.update(key, value, ttlHours).segment.delete()returnsnull(not an error) if the key is missing.
Triggers
Use this skill for: "Cache", "cache segment", "cache key", "cache value", "TTL", "in-memory store", segment.get, segment.put, segment.delete, "session data", "temporary data Catalyst", "cache vs Data Store", or "48-hour cache".
References
| Reference | Load when the query is about… |
|---|---|
references/cache-basics.md |
SDK operations (get, put, delete, update), Segment ID, 48hr TTL max, string-only values, segment.delete() null gotcha, segment.update() TTL gotcha |
What ships with it
1 file 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.
- 2d ago First seen · 26 lines · 53 tokens per session scan A a22b4a8f7586
catalyst-cache is a skill published in the GitHub repository catalystbyzoho/claude-plugin (0 stars, last pushed 20d ago), licensed Apache-2.0. It adds 53 tokens to every session and 458 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.