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/mohocp/dataecho/dataecho-memorynpx skills add mohocp/dataecho --skill dataecho-memorygit clone --depth 1 https://github.com/mohocp/dataechoWhat 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.00103 | $0.01658 |
| Opus 5 | $0.00051 | $0.00829 |
| Sonnet 5 | $0.00021 | $0.00332 |
| Haiku 4.5 | $0.00010 | $0.00166 |
Grade C, and why
dataecho-memory scanned grade C with 3 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -sS -X POST https://dataecho.ai/api/auth/agent/request-code -H 'content-type: application/json' -d '{"email":"[email protected]"}' Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
echo '<API_KEY>' > ~/.artifact/credentials && chmod 600 ~/.artifact/credentials Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -X POST https://dataecho.ai/api/auth/agent/request-code -H 'content-type: application/json' -d '{"email":"[email protected]"}' How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DataEcho Memory — remember things across sessions
Your context window dies with the session. This skill gives you a memory that doesn't:
a private, versioned drive on https://dataecho.ai holding one small index (MEMORY.md)
plus one file per fact (memories/<slug>.md). Reading the index costs ~1 KB; everything
else loads on demand. Works from any machine or throwaway sandbox — only the API key travels.
scripts/memory.sh sits next to this file (bash + python3 stdlib, no other deps).
Session protocol — this is the discipline that makes memory work
- Recall first. At the start of a session (or when the user references past work), run
scripts/memory.sh recall. It prints the index — every memory as one line. Cheap; do it. - Load selectively.
recall <query>fetches only the fact files whose index line matches. Never dump the whole store into context unless asked (recall --full). - Remember durable things, at the moment you learn them:
- the user states a preference or corrects you →
--type user - a decision is made and has a why →
--type decision - you learn something non-obvious the next session will need →
--type insight - a work session ends mid-task →
--type task(state + next step) - a URL/dashboard/ticket worth keeping →
--type referenceDo NOT save: secrets or API keys (memory is not a vault), anything derivable from the repo/git history, or session-scoped trivia.
- the user states a preference or corrects you →
- Update, don't duplicate.
rememberwith an existing slug updates it (and tells you). Before creating,recalla keyword — if a related memory exists, re-remember the same slug with merged content. The script warns you when a new slug looks like an existing one. - Forget what's wrong. A false memory is worse than none:
memory.sh forget <slug>. - Memories age. They record what was true when written. If one names a file, URL, or flag, verify it still exists before acting on it. Convert relative dates ("yesterday", "next week") to absolute dates when writing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 120 lines · 103 tokens per session scan C 3966cb06523e
dataecho-memory is a skill published in the GitHub repository mohocp/dataecho (0 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 1,658 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 3 findings (sends data to an external url, asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memory-quality
Audits and cleans up Claude Code auto-saved memory files. Scores on 4 dimensions, detects conflicts, opens a visual dashboard. Trigger on: memories, memory quality, memory cleanup, memory health, memory dashboard, 检查记忆, 清理记忆, 记忆质量, 记忆看板.
命理解读师
Skill "命理解读师" from learnwithu/mingli-master, covering 命理解读师 v2, 核心原则, 禁忌, 依赖 and 工作流程.
os-whats-next
ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is…
skill-authoring
Author SKILL.md: frontmatter, structure, writing principles.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.