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 skills add gebeer/processwire-ai-docs --skill processwire-memorygit clone --depth 1 https://github.com/gebeer/processwire-ai-docsWrote 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/gebeer/processwire-ai-docs/processwire-memory)<a href="https://agentmods.dev/skills/gebeer/processwire-ai-docs/processwire-memory"><img src="https://agentmods.dev/badge/skills/gebeer/processwire-ai-docs/processwire-memory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gebeer/processwire-ai-docs/processwire-memory"><img src="https://agentmods.dev/badge/skills/gebeer/processwire-ai-docs/processwire-memory.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.01579 |
| Opus 5.5 | $0.00023 | $0.00632 |
| Sonnet 5.5 | $0.00012 | $0.00316 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
processwire-memory 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 1mo 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
memvid -- ProcessWire Cross-Project Memory
Installation
npm install -g memvid-cli
If the memory file doesn't exist yet:
mkdir -p ~/.memvid && memvid create ~/.memvid/processwire.mv2
When to Store vs Retrieve
STORE proactively when you discover:
- Non-obvious PW API pattern, gotcha, or workaround
- Debugging insight involving ProcessWire internals
- PW convention or architectural decision worth preserving
- Correction to previously stored PW knowledge
- User requests storing a PW pattern
RETRIEVE when:
- Starting any ProcessWire task
- Encountering a PW error or familiar pattern
- User asks "do we know..." or "have we seen..." about PW
- Before PW architectural decisions
DO NOT store:
- Project-specific config (belongs in project CLAUDE.md)
- Transient debugging state (one-off errors)
- Non-PW knowledge (general PHP, CSS, JS patterns)
URI Convention
mv2://processwire/topic/subtopic
| Topic | Example URIs |
|---|---|
| api/pages | mv2://processwire/api/pages -- $pages API, PageArray, find/get |
| api/fields | mv2://processwire/api/fields -- field types, options, config |
| api/templates | mv2://processwire/api/templates -- template API, families |
| api/hooks | mv2://processwire/api/hooks -- hook system, priorities, events |
| api/modules | mv2://processwire/api/modules -- module API, autoload, config |
| selectors | mv2://processwire/selectors -- selector syntax, operators |
| templating | mv2://processwire/templating -- template files, rendering, regions |
| multilingual | mv2://processwire/multilingual -- LanguageSupport, translations |
| permissions | mv2://processwire/permissions -- access control, roles, pages |
| debugging | mv2://processwire/debugging -- common errors, diagnostics |
| patterns | mv2://processwire/patterns -- architectural patterns, conventions |
| migrations | mv2://processwire/migrations -- field/template setup, deployment |
Use --scope on retrieval to filter by URI prefix.
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.
- 1mo ago First seen · 167 lines · 58 tokens per session scan A 515d4dcc031d
processwire-memory is a skill published in the GitHub repository gebeer/processwire-ai-docs (11 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 1,579 once invoked, about $0.0002 per session on Opus 5.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
mem0-status
Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, addmemory errors occur, or to verify the plugin is working correctly.
status
Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.
supermemory
Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
browserwing-executor
Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.
potpie-repo-baseline
Use when establishing, refreshing, or deeply understanding a repository's baseline memory in Potpie: purpose, application type, features, services/modules, environments, deploy shape, dependencies, API contracts, datastores, integrations, ownership, and explicit preferences. The harness reads authored and…