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/ohad6k/emulo/minenpx skills add ohad6k/emulo --skill minegit clone --depth 1 https://github.com/ohad6k/emuloWrote 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/ohad6k/emulo/mine)<a href="https://agentmods.dev/skills/ohad6k/emulo/mine"><img src="https://agentmods.dev/badge/skills/ohad6k/emulo/mine.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 | $0.00033 | $0.00548 |
| Opus 5 | $0.00016 | $0.00274 |
| Sonnet 5 | $0.00007 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
mine 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 4d 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
Emulo mine
Mine only real user-authored .jsonl sessions. Never synthesize a profile from rules files, memory, or a typed self-description.
- Resolve
EMULO_PYtoemulo.pytwo directories above this skill, falling back to./emulo.pyonly in a direct checkout. Confirm Python 3 exists. - The full-history quality default reads all eligible history. Run read-only
python "$EMULO_PY" plugin preflight, show valid sessions, post-dedupe source tokens, selected source tokens, cache hits, planned worker calls, and planned reducer calls, then wait for explicit cost approval before model work. - Only when the user explicitly asks for a quick preview, run preflight and prepare with
--preview. Say this exactly before approval:Quick preview creates a starter profile from selected history, not the full profile.Never call preview the default, the full profile, or equivalent in quality to full-history mining. - Retain the displayed
approval_hash. Runpython "$EMULO_PY" plugin prepare --approved-plan-hash HASHwith the exact approved mode. If the hash changed, show the new plan and obtain approval again. Retain the exactrun_id, selected segment/report paths, andpack_path. - Run one fast worker for each uncached selected segment. Each reads only its segment and the per-segment contract in
MINING_PROMPT.md, writes its assigned JSON report, and runs the read-onlyplugin validate-reportcommand until accepted. - Cache each accepted report with
plugin cache-report; stop on rejection. - Run one strongest-available reducer over only the validated reports and the combined reducer contract. It writes the complete assigned pack and self-validates with
plugin validate-pack. - Activate only the validated pack with
plugin activate, then runplugin statusand render the card. Report active version, domain states, selected source tokens, actual worker/reducer passes, cache reuse, and targeted-deepen instructions.
Every prepared mode requires explicit approval of its displayed plan. Installation itself scans no logs and schedules zero mining calls. An identical update schedules zero additional Emulo mining calls, although the host task still has normal interaction overhead.
Adaptive receipt/scout stages are experimental and excluded from the Plugin release path. Run --stage A only when a developer explicitly requests experimental adaptive-recall testing; never select it automatically or use it for release calibration.
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.
- 4d ago First seen · 22 lines · 33 tokens per session scan A 291f4233a191
mine is a skill published in the GitHub repository ohad6k/emulo (287 stars, last pushed 10d ago), licensed MIT. It adds 33 tokens to every session and 548 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-30.
Other skills, from other repositories
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Pinned, always-injected.
plur-memory
Your memory stays on your machine. No cloud, no tracking, no API key. PLUR makes your OpenClaw remember — and shares that memory with every other tool you use.
mengram-memory
Long-term memory with 3 types (facts, events, workflows). Remember user preferences, past conversations, and learned procedures across sessions. Use when recalling what the user said before, saving important info, getting user context, or tracking completed workflows.
honcho-integration
Integrate Honcho memory into existing Python or TypeScript codebases. Use when adding Honcho SDK, setting up peers, configuring sessions, and accessing Honcho's representation.
honcho-memory
Concepts and strategy for using a connected Honcho as persistent memory of the user — the recall/record loop and session and peer design. Start here to understand how Honcho memory works, then connect — via a first-class integration for your environment if one exists (preferred), or raw MCP tools (covered here) or the…