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 Opita-Code/dark-memory-mcp --skill dark-memorygit clone --depth 1 https://github.com/Opita-Code/dark-memory-mcpWrote 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/opita-code/dark-memory-mcp/dark-memory)<a href="https://agentmods.dev/skills/opita-code/dark-memory-mcp/dark-memory"><img src="https://agentmods.dev/badge/skills/opita-code/dark-memory-mcp/dark-memory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/opita-code/dark-memory-mcp/dark-memory"><img src="https://agentmods.dev/badge/skills/opita-code/dark-memory-mcp/dark-memory.svg" alt="Reviewed on agentmods" width="80" 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.00353 | $0.07831 |
| Opus 5.5 | $0.00141 | $0.03132 |
| Sonnet 5.5 | $0.00071 | $0.01566 |
| Haiku 4.5 | $0.00035 | $0.00783 |
Grade A, and why
dark-memory scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
not a code bug. Verify with curl before touching the Go code. The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 469 lines · 353 tokens per session scan A 1a238c2ca9c9
dark-memory is a skill published in the GitHub repository Opita-Code/dark-memory-mcp (1 stars, last pushed 2d ago), with no licence file. It adds 353 tokens to every session and 7,831 once invoked, about $0.0014 per session on Opus 5.5. A static security scan graded it A with 1 finding (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
agentbook-version-control
Coordinate Git and Cross-Session Memory as version control for agent work. Use when Codex needs AgentBook status, checkpoints, history, resume or handoff, provenance, isolated agent approaches, semantic comparison, or an evidence-backed game-development tuning and playtest iteration with an explicit keep or revert…
csm-continuity
Use the complete native Cross-Session Memory (CSM) runtime for continuity, memory governance, living state, beliefs, self-model, AgentBook, checkpoints, context cache, goals, work ledger, compaction, re-entry, or handoff across Codex tasks.
csm-governance
Safely deduplicate, review, merge, and archive Cross-Session Memory. Use when memory needs cleanup, dedup, merge, archive-candidate review, or recall-quality assessment.
wiki-lint
Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.
wiki-status
Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.
wiki-dashboard
Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.