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 commands/evermind-ai/everos/debuggit clone --depth 1 https://github.com/EverMind-AI/EverOSWhat 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.00012 | $0.00405 |
| Opus 5 | $0.00006 | $0.00202 |
| Sonnet 5 | $0.00002 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
debug 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 yesterday.
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
EverMem Debug Log Viewer
View the EverMem debug log to troubleshoot issues.
Instructions
Show the user the recent debug log entries from /tmp/evermem-debug.log.
- First check if debug mode is enabled by looking for
EVERMEM_DEBUG=1in the plugin's.envfile - Read the last 50 lines of the debug log file
- If the file doesn't exist or is empty, inform the user how to enable debug mode
Actions
-
Check debug mode status:
grep "EVERMEM_DEBUG" /path/to/plugin/.env 2>/dev/null || echo "Not configured" -
Show recent logs:
tail -50 /tmp/evermem-debug.log 2>/dev/null || echo "No debug log found" -
Format the output for the user, highlighting:
[inject]entries for memory retrieval[store]entries for memory saving- Any errors or warnings
Output Format
📋 EverMem Debug Log
Status: Debug mode [ENABLED/DISABLED]
Log file: /tmp/evermem-debug.log
--- Recent Entries ---
[timestamp] [inject] ...
[timestamp] [store] ...
--- Tips ---
• Enable debug: Add EVERMEM_DEBUG=1 to .env
• Clear log: > /tmp/evermem-debug.log
• Live view: tail -f /tmp/evermem-debug.log
Additional Options
If the user specifies arguments:
clear- Clear the debug loglive- Show command for live monitoringfull- Show more lines (100+)inject- Filter to show only [inject] entriesstore- Filter to show only [store] entries
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.
- yesterday First seen · 60 lines · 12 tokens per session scan A 7e756746f09b
debug is a command published in the GitHub repository EverMind-AI/EverOS (12,594 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 405 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 commands, from other repositories
compass-search
Search compass session-summary frontmatter (name, concept, type, drift, body) across all recorded sessions. Returns ranked hits with timestamps and drift glyphs.
compass-verify
Verify the Merkle hash chain over /.claude/projects/ /memory/ and report any tampered or missing files.
discover
Build or refresh the on-demand discovery map (concept graph + per-node notes).
aria
Command "aria" from mikeprasad/aria-knowledge, covering /aria, common actions and codex notes.
kol-analyze
分析达人数据并给出投放评级和报价建议。.
kol-daily
获取今日KOL跟进任务清单。.