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 BongSuCHOI/memex --skill analyzing-all-conversationsgit clone --depth 1 https://github.com/BongSuCHOI/memexWrote 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/bongsuchoi/memex/analyzing-all-conversations)<a href="https://agentmods.dev/skills/bongsuchoi/memex/analyzing-all-conversations"><img src="https://agentmods.dev/badge/skills/bongsuchoi/memex/analyzing-all-conversations.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.00047 | $0.00387 |
| Opus 5 | $0.00023 | $0.00193 |
| Sonnet 5 | $0.00009 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
analyzing-all-conversations 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 7d 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
Analyzing All Conversations
Resolve PLUGIN_ROOT as two directories above this skill directory.
Establish coverage
Run the deterministic, read-only report before interpreting the corpus:
node "$PLUGIN_ROOT/cli/runtime-exec.js" memex analyze --json
Use its conversation/session/exchange/project/date totals, extraction and summary coverage, fact counts, domains, project rollups, timeline, and recommendations. Never recreate those numbers from sampled search results.
Close or disclose gaps
If requested and recommended by the report, start only the relevant explicit backfill:
node "$PLUGIN_ROOT/cli/runtime-exec.js" memex backfill extract --background
node "$PLUGIN_ROOT/cli/runtime-exec.js" memex backfill ontology --background
node "$PLUGIN_ROOT/cli/runtime-exec.js" memex sync
A started background worker is 진행 중, not complete. Re-run status --json
only when the user needs a settled coverage result; otherwise report the exact
pending counts and log path.
Add meaning
Use graph_stats for the scoped graph overview, search_facts for representative
decisions/patterns/constraints, and cross_project_insights only with an explicit
canonical current project. Produce the report in the user's language with:
- overall corpus and date range;
- extraction/summary coverage;
- project rollups and representative knowledge;
- domain/category distribution;
- activity timeline;
- remaining gaps and actions actually started.
Do not claim full coverage unless every required pending/missing counter is zero.
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.
- 7d ago First seen · 51 lines · 47 tokens per session scan A 3f1d191de3bc
analyzing-all-conversations is a skill published in the GitHub repository BongSuCHOI/memex (0 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 387 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
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website"…
potpie-graph
Use when the task can read or write the project-memory graph through the potpie CLI: discover the contract with graph catalog, read named views with graph read, resolve entity identity with graph search-entities, create validated plans with graph propose, commit plans with graph commit --verify, inspect quality with…
potpie-repo-baseline
Use when establishing, refreshing, or deeply understanding a repository's baseline memory in Potpie: purpose, application type, features, services/modules, environments, deploy shape, dependencies, API contracts, datastores, integrations, ownership, and explicit preferences. The harness reads authored and…
potpie-project-preferences
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
hybrid-memory
Hybrid memory strategy combining OpenClaw's built-in QMD vector memory with Graphiti temporal knowledge graph. Use for all memory recall requests.