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 commands/ariegoldkin/claude-forge/semantic-cachinggit clone --depth 1 https://github.com/ArieGoldkin/claude-forgeWrote 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/commands/ariegoldkin/claude-forge/semantic-caching)<a href="https://agentmods.dev/commands/ariegoldkin/claude-forge/semantic-caching"><img src="https://agentmods.dev/badge/commands/ariegoldkin/claude-forge/semantic-caching.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.00056 | $0.00092 |
| Opus 5 | $0.00028 | $0.00046 |
| Sonnet 5 | $0.00011 | $0.00018 |
| Haiku 4.5 | $0.00006 | $0.00009 |
Grade A, and why
semantic-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 4d 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
semantic-caching
Invoking skill: atk:semantic-caching
Follow the instructions in the semantic-caching skill exactly.
$ARGUMENTS
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.
- 4d ago First seen · 12 lines · 56 tokens per session scan A 2914b1eca96e
semantic-caching is a command published in the GitHub repository ArieGoldkin/claude-forge (6 stars, last pushed 27d ago), licensed MIT. It adds 56 tokens to every session and 92 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-31.
Other commands, from other repositories
cache-manage
Command "cache-manage" from ruvnet/RuView, covering cache-manage, usage, options, examples and view cache stats.
redis
This API allows you to manage your Managed Databases for Redis™.
index-management
Create, inspect, and drop search indexes. Wait for indexing to complete after data changes. Indexes automatically track Redis keys matching a specified prefix.
cloudflare-kv:test
Test KV namespace connection and operations - validates configuration, performs CRUD tests, and reports diagnostics.
v-memory-refresh
(Re)index docs/superpowers prose into the local V-memory cache so recall is current. Incremental by file hash; runs fully offline (FTS5, pure stdlib). Optionally enable the semantic lane with a one-time bootstrap. Run it after pulling new docs, or when /v:remember looks stale.
laravel-performance-cache
Add caching to reduce work; use the laravel:performance-caching skill exactly as written.