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 crcresearch/llm-wiki-memory-template --skill wiki-experimentgit clone --depth 1 https://github.com/crcresearch/llm-wiki-memory-templateWrote 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/crcresearch/llm-wiki-memory-template/wiki-experiment)<a href="https://agentmods.dev/skills/crcresearch/llm-wiki-memory-template/wiki-experiment"><img src="https://agentmods.dev/badge/skills/crcresearch/llm-wiki-memory-template/wiki-experiment.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.00038 | $0.01097 |
| Opus 5 | $0.00019 | $0.00549 |
| Sonnet 5 | $0.00008 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
wiki-experiment 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 8d 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.
- 8d ago First seen · 46 lines · 38 tokens per session scan A f8d79eb5ce41
wiki-experiment is a skill published in the GitHub repository crcresearch/llm-wiki-memory-template (4 stars, last pushed 11d ago), with no licence file. It adds 38 tokens to every session and 1,097 once invoked, about $0.0002 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 skills, from other repositories
godot-optimization
Use when optimizing Godot games — profiler, draw calls, physics tuning, memory management, and common bottlenecks.
evo-memory
Manages persistent research memory across ideation and experimentation cycles. Maintains two stores: Ideation Memory MI (feasible/unsuccessful directions) and Experimentation Memory ME (reusable strategies for data processing, model training, architecture, debugging). Three evolution mechanisms: IDE (after…
swmm-modeling-memory
Read historical Agentic SWMM experiment audit artifacts and summarize repeated assumptions, QA issues, failures, missing evidence, run-to-run differences, lessons learned, and controlled skill update proposals. Use downstream of swmm-experiment-audit when multiple audited runs exist or when a user asks for modeling…
calculator
Math calculations, unit conversions, date/time arithmetic, and currency rates. Python-powered, no API needed for math.
agent-auto-sci-automation
A guide for turning research projects into lasting local workflows with source tracking, structured notes, experiments, paper planning, reviews, and checkpoints. It also describes a shared memory system for research materials.
evolving-memory
Evolving memory system inspired by EvoScientist. Extends ScienceClaw's research memory with four record types (finding, ideation, strategy, pitfall) to enable learning from past research sessions. Recall relevant strategies and pitfalls before recipe execution, extract and persist new lessons after completion. Use at…