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/christopherkarani/wax/maintenancenpx skills add christopherkarani/Wax --skill maintenancegit clone --depth 1 https://github.com/christopherkarani/WaxWrote 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/christopherkarani/wax/maintenance)<a href="https://agentmods.dev/skills/christopherkarani/wax/maintenance"><img src="https://agentmods.dev/badge/skills/christopherkarani/wax/maintenance.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.00018 | $0.00258 |
| Opus 5 | $0.00009 | $0.00129 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
wax-memory-maintenance 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
Wax Memory Maintenance
Use when the active Hermes memory provider is wax-memory.
Checks
- Confirm the broker is reachable:
hermes wax-memory doctor - Prefer
wax_recallfor assembled context andwax_searchfor raw hits - Store durable facts with
wax_rememberandmemory_typefromnote,user_preference,decision,lesson,handoff,constraint,fact;task_stateis session-local working state and requires an active session - Write session continuity with
wax_handoff; do not dump raw transcripts - Use structured tools (
wax_entity_upsert,wax_fact_assert,wax_facts_query) only for stable knowledge-graph facts
Recovery
- If recall is empty, run
npx waxmcp --embedder minilm --transport http - If vector search is disabled, rebuild both
wax-cliandwax-mcpwith MiniLM/Arctic traits - After
/resetor/resume, rely on the provider session switch — do not invent a new session id
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 · 23 lines · 18 tokens per session scan A 213df92671b4
wax-memory-maintenance is a skill published in the GitHub repository christopherkarani/Wax (790 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 258 once invoked, about $0.0001 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
dataframe-performance
Decides when pandas is fine and when to reach for Polars, plus vectorisation, dtype, and memory technique either way. Use when an operation such as a groupby, join, or apply is slow, or a script takes far longer than it should. Use when a dataset no longer fits in memory. Use when someone asks about Polars…
ds-evaluate
Measures how a model really performs — the metric at a stated operating point, a confusion matrix, calibration, and performance broken out by slice rather than one aggregate number. Use when someone asks how well a model does on held-out data, wants precision and recall at a threshold, or wants a confusion matrix. Use…
metric-selection
Picks the evaluation metric that matches the decision and the shape of the target, and says plainly when a familiar one is wrong. Use when someone asks whether accuracy is the right thing to report, or whether to optimise for precision or recall. Use when choosing or defending a metric for classification, regression…
dask
Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed…
get-available-resources
This skill should be used at the start of any computationally intensive scientific task to detect and report available system resources (CPU cores, GPUs, memory, disk space). It creates a JSON file with resource information and strategic recommendations that inform computational approach decisions such as whether to…
polars
Fast in-memory DataFrame library for datasets that fit in RAM. Use when pandas is too slow but data still fits in memory. Lazy evaluation, parallel execution, Apache Arrow backend. Best for 1-100GB datasets, ETL pipelines, faster pandas replacement. For larger-than-RAM data use dask or vaex.