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/askgit 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.00017 | $0.00387 |
| Opus 5 | $0.00009 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
ask 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 2d 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
EverMem Ask
Answer a question using both memory search results and current conversation context.
Question
{{question}}
Instructions
-
Search memories using
evermem_searchMCP tool with relevant keywords. Start with 10 results. -
Evaluate results:
- If memories provide useful context, note what you learned
- If more detail needed, search again with different keywords (up to 3 searches)
- If no relevant memories found, that's OK - proceed with what you know
-
Combine sources to answer:
- Memory search results (past sessions)
- Current conversation context (this session)
- Your general knowledge (when applicable)
-
Be honest about sources:
- "Based on our discussion on [date]..." - when citing memory
- "From our current session..." - when citing current context
- "I don't have any recorded information about this" - when memories don't help
- "Based on general best practices..." - when using general knowledge
-
Admit uncertainty:
- If memories are incomplete or unclear, say so
- If you're inferring rather than recalling, make that clear
- It's better to say "I don't know" than to guess
Response Format
Start with a direct answer, then provide supporting context:
[Direct answer to the question]
**From memories:**
- [Relevant points from past sessions, with dates]
**Current context:**
- [Relevant points from this session, if any]
**Note:** [Any caveats or gaps in knowledge]
Now answer the user's question.
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.
- 2d ago First seen · 58 lines · 17 tokens per session scan A 488f7e1a60d6
ask is a command published in the GitHub repository EverMind-AI/EverOS (12,624 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 387 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
README
Git workflow and quality assurance commands for the claude-skills repository.
research-perplexity
Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.