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/aristoapp/claude-membase/wikinpx skills add aristoapp/claude-membase --skill wikigit clone --depth 1 https://github.com/aristoapp/claude-membaseWrote 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/aristoapp/claude-membase/wiki)<a href="https://agentmods.dev/skills/aristoapp/claude-membase/wiki"><img src="https://agentmods.dev/badge/skills/aristoapp/claude-membase/wiki.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.00023 | $0.00232 |
| Opus 5 | $0.00012 | $0.00116 |
| Sonnet 5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
membase-wiki 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 5d 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
Membase Wiki
Use wiki for factual knowledge that should behave like documentation:
- project architecture notes
- onboarding docs
- external references
- stable technical specifications
- handoff documents
Use search_wiki for retrieval and add_wiki / update_wiki for document
management. When adding or updating wiki content, preserve the full artifact
body unless the user explicitly asks to save a summary. If the user names a
Project, pass it as project; new Projects are created automatically. A
Project is the Wiki filing location and is separate from the document title.
Leave project empty when the user does not name one. After add/update, report
the returned destination, such as Saved to Project: X, Saved to Basic, or
Moved to Basic.
Use delete_wiki only after explicit user confirmation, and pass
confirm: true. Use memory, not wiki, for user preferences, habits, or
personal context.
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.
- 5d ago First seen · 28 lines · 23 tokens per session scan A 934469627116
membase-wiki is a skill published in the GitHub repository aristoapp/claude-membase (3 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 232 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-31.
Other skills, from other repositories
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
cco-templates
Manage context templates for common task types.
knowledge-priming-refiner
Facilitate a structured conversation to create a project-specific knowledge base document. Produces a knowledge-base.md that primes AI with the project's tech stack, architecture, trusted sources, and project structure. Use when the user says 'set up knowledge base', 'prime the project', 'onboard AI', 'create…