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 agents/s3rgiosan/wp-agents/wp-mnemongit clone --depth 1 https://github.com/s3rgiosan/wp-agentsWrote 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/agents/s3rgiosan/wp-agents/wp-mnemon)<a href="https://agentmods.dev/agents/s3rgiosan/wp-agents/wp-mnemon"><img src="https://agentmods.dev/badge/agents/s3rgiosan/wp-agents/wp-mnemon.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.00071 | $0.00399 |
| Opus 5 | $0.00036 | $0.00199 |
| Sonnet 5 | $0.00014 | $0.00080 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
wp-mnemon 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 37 lines · 71 tokens per session scan A 7826ac1cbe8b
wp-mnemon is an agent published in the GitHub repository s3rgiosan/wp-agents (5 stars, last pushed 1mo ago), with no licence file. It adds 71 tokens to every session and 399 once invoked, about $0.0004 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 agents, from other repositories
knowledge-manager
Comprehensive knowledge management agent that processes multiple input sources (web, files, Notion, images) and exports to various formats (Obsidian, Notion, Markdown, PDF, blogs).
performance-optimizer
Performance optimization expert. Use for profiling, bottleneck analysis, latency issues, memory problems, and scaling strategies. Triggers: performance, slow, latency, profiling, optimization, bottleneck, scaling.
doc-writer
Documentation expert creating crystal-clear docs. Use after feature completion.
wiki-ingest
Parallel batch ingestion agent for the Obsidian wiki vault. Dispatched when multiple sources need to be ingested simultaneously. Processes one source fully (read, extract, file entities and concepts, update index) then reports what was created and updated. Use when the user says "ingest all", "batch ingest", or…
008-documentation
Document the context hierarchy and memory system comprehensively.
embedded-engineer
An embedded engineer who develops firmware and software for resource-constrained devices — thinking in memory budgets, real-time constraints, power consumption, and hardware-software interfaces. Use for firmware design, embedded systems architecture, RTOS decisions, and hardware-software co-design.