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.
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/cache-invalidate)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/cache-invalidate"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/cache-invalidate.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.1 | $0.00016 | $0.00748 |
| Opus 5 | $0.00008 | $0.00374 |
| Sonnet 5 | $0.00003 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
cache-invalidate 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.
This is a copy
100% identical to cache-invalidate — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cache-invalidate
🦉 Savia invalida solo la capa que cambió — fino, no brusco.
Cargar perfil de usuario
Grupo: Context Engineering — cargar:
workflow.md— para validar impacto de invalidación
Ver docs/rules/domain/context-map.md.
Parámetros
--layer tools|system|rag|conversation Capa a invalidar (por defecto: todas)
--selective Invalidación granular vs. full flush
--lang es|en Idioma del output
Flujo
Paso 1 — Verificar caché actual
- Leer estado del caché:
$HOME/.pm-workspace/cache-state.json - Mostrar: tamaño total, por capa, timestamp creación, edad fragmentos
Paso 2 — Detectar cambios (para --selective)
Si --selective: detectar qué cambió en .git/index:
- Tools: cambios
docs/rules/→ invalidar TOOLS - System: cambios CLAUDE.md → invalidar SYSTEM
- RAG: cambios
docs/→ invalidar RAG - Conversation: comandos ejecutados → invalidar CONVERSATION
Paso 3 — Proponer invalidación
Sin --layer (auto):
🔄 Invalidación Automática
Layers afectadas:
├─ ✅ TOOLS (cambios reglas) → Invalidar
├─ ✅ SYSTEM (cambios CLAUDE.md) → Invalidar
├─ ✅ RAG (cambios docs) → Invalidar
└─ ⏸️ CONVERSATION (en sesión) → Mantener
¿Proceder? (y/n)
Paso 4 — Crear backup pre-invalidación
- Guardar snapshot:
$HOME/.pm-workspace/cache-backups/cache-{timestamp}.json.bak - Registrar qué se invalidó
- Mostrar ruta del backup
Paso 5 — Ejecutar invalidación
Granular (--selective):
- Marcar fragmentos como "stale" en
cache-state.json - No borrar — dejar que expiren según TTL
- Cuando se acceda → recargar
Full flush (sin --selective):
- Borrar layer completa
- Próximo comando → recarga completa
Mostrar:
✅ Invalidación Completada
Layer TOOLS: 45 ficheros invalidados
Layer SYSTEM: 1 fichero invalidado
Layer RAG: 12 ficheros invalidados
Impacto: próximos comandos +3s latencia
Paso 6 — Registrar rollback
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 · 122 lines · 16 tokens per session scan A e5a4938f174c
cache-invalidate is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 748 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cache-invalidate, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
laravel-ai-sdk
Build AI features with the first-party Laravel AI SDK (Laravel 13+); use the laravel:ai-sdk skill exactly as written.
audit-prompt
Evaluate an existing prompt for clarity, effectiveness, and edge cases.
develop-image-prompt.eval
Generates a detailed image generation prompt from a document or content description. Good output: a prompt that is specific, visual, non-abstract, includes style/composition/lighting guidance, and is calibrated to the specified dimensions and style options.
dare-llm-integration
Integração segura e eficiente com LLMs (Gemini, Claude, OpenAI, Ollama) em projetos DARE.
prompt-create
Create a new prompt following ground rules.
vlm-ocr-evaluation
Run the vlm-ocr skill in its evaluate phase: compare candidate OCR systems against a stratified human-transcribed ground-truth sample and pick a model on measured CER/WER before committing to a bulk run.