cache

A command for managing the local cache used by the mcp-standards tool. A cache is stored data kept locally so files can be reused without fetching them again.

In plain words
What is it for?
Use it to list cached files, clear all or outdated entries, export or import a cache, analyze its usage, verify its integrity, and set or check a size limit.
Why use it?
It helps inspect, clean, move, analyze, and verify cached standards files, including removing files that are outdated or exceed a size limit.

Command

Install

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.

agentmods
npx agentmods add commands/williamzujkowski/mcp-standards-server/cache
Clone the repo
git clone --depth 1 https://github.com/williamzujkowski/mcp-standards-server
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,908 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01908
Opus 5 $0.00000 $0.00954
Sonnet 5 $0.00000 $0.00382
Haiku 4.5 $0.00000 $0.00191

Measured 2d ago against content hash ea5557056e90, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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.

docs/cli/commands/cache.md · 337 lines

How it starts

The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cache Command

Manage the local standards cache.

Synopsis

mcp-standards cache [options]

Description

The cache command provides tools for managing the local cache of standards files, including listing, clearing, exporting, and analyzing cached content.

Options

--list

List all cached files with details.

mcp-standards cache --list

--clear

Clear all cached files.

mcp-standards cache --clear

--clear-outdated

Clear only outdated files (based on TTL).

mcp-standards cache --clear-outdated

--export <path>

Export cache to a directory or archive.

mcp-standards cache --export /path/to/export
mcp-standards cache --export backup.tar.gz

--import <path>

Import cache from a directory or archive.

mcp-standards cache --import /path/to/import
mcp-standards cache --import backup.tar.gz

--analyze

Analyze cache usage and provide statistics.

mcp-standards cache --analyze

--verify

Verify cache integrity.

mcp-standards cache --verify

--size-limit <MB>

Set or check cache size limit.

mcp-standards cache --size-limit 500

Examples

List Cached Files

mcp-standards cache --list

Output:

Cached files (25):

web-development/
  html5-standards.yaml (12.3 KB) - cached 2h ago, expires in 22h
  css3-standards.yaml (15.7 KB) - cached 2h ago, expires in 22h
  javascript-es2025.yaml (23.1 KB) - cached 2h ago, expires in 22h

api-design/
  rest-api-standards.yaml (18.9 KB) - cached 25h ago, OUTDATED
  graphql-standards.yaml (21.4 KB) - cached 2h ago, expires in 22h

testing/
  javascript-testing.yaml (16.2 KB) - cached 2h ago, expires in 22h
  python-testing.yaml (14.8 KB) - cached 2h ago, expires in 22h

Total: 25 files, 3.42 MB
Outdated: 1 file
Cache directory: /home/user/.cache/mcp-standards

Clear Cache

# Clear all cached files
mcp-standards cache --clear

Output:

Clearing cache...
Removed 25 files (3.42 MB)
Cache cleared successfully!

Read the full file on GitHub · 337 lines

Changes

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.

  1. 2d ago First seen · 337 lines · 0 tokens per session scan A ea5557056e90

Subscribe to this mod's changes

cache is a command published in the GitHub repository williamzujkowski/mcp-standards-server (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,908 tokens. 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.