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.
git clone --depth 1 https://github.com/EverMind-AI/EverMeWrote 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/commands/evermind-ai/everme/everme-help)<a href="https://agentmods.dev/commands/evermind-ai/everme/everme-help"><img src="https://agentmods.dev/badge/commands/evermind-ai/everme/everme-help/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/commands/evermind-ai/everme/everme-help"><img src="https://agentmods.dev/badge/commands/evermind-ai/everme/everme-help.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.00011 | $0.00236 |
| Opus 5.5 | $0.00004 | $0.00094 |
| Sonnet 5.5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
everme-help 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.
What it actually says
EverMe · help
Print the following block verbatim to the user:
EverMe for Claude Code
─────────────────────
Auth: EVERME_API_KEY (account emk_*) — recall-only mode
EVERME_AGENT_TOKEN + EVERME_AGENT_ID — required for realtime writes
Gateway: EVERME_API_BASE — defaults to https://api.everme.evermind.ai
Hooks:
SessionStart → loads the durable Profile snapshot
UserPromptSubmit → recalls relevant memories before each prompt
Stop → saves the last raw turn through /mem/agent-memory
SessionEnd → no persistence; Stop owns runtime writes
Slash:
/recall <query> — explicit search + summarize
/everme-help — this card
MCP tools:
mem_search — hybrid search across all memory buckets
mem_context — durable Profile snapshot only
mem_save_fact — save a durable user fact to the Profile path
mem_save_turn — save a reusable task trajectory
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 · 32 lines · 11 tokens per session scan A 0373b503c36f
everme-help is a command published in the GitHub repository EverMind-AI/EverMe (68 stars, last pushed 4d ago), licensed Apache-2.0. It adds 11 tokens to every session and 236 once invoked, about $0.0000 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-30.
Other commands, from other repositories
save
Save confirmed decisions, constraints and lessons from this conversation as structured project context.
compact
Summarize the requested conversation and upload a Markdown archive named after the working directory to Kireo.
resume
Load previously saved project context to continue work, including constraints, open threads and decisions.
krimto-status
Show the current state of Krimto memory — total facts, scope breakdown, recent writes, and index health.
init
Initialize configurations for Supabase local development.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.