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 corbym/memoryweb --skill memorywebgit clone --depth 1 https://github.com/corbym/memorywebWrote 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/corbym/memoryweb/memoryweb)<a href="https://agentmods.dev/skills/corbym/memoryweb/memoryweb"><img src="https://agentmods.dev/badge/skills/corbym/memoryweb/memoryweb/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/corbym/memoryweb/memoryweb"><img src="https://agentmods.dev/badge/skills/corbym/memoryweb/memoryweb.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.00050 | $0.05756 |
| Opus 5.5 | $0.00020 | $0.02302 |
| Sonnet 5.5 | $0.00010 | $0.01151 |
| Haiku 4.5 | $0.00005 | $0.00576 |
Grade A, and why
memoryweb 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
memoryweb — Agent Instructions
Two layers, kept deliberately separate: a short imperative contract up top, reference material below it. Position determines compliance — instructions that only live in reference material get skipped, not from disagreement, but because agents never reach them.
Layer 1 — Behavioural Contract
Silent operations. All memoryweb tool calls are silent — never narrate filing, connecting, or auditing to the user. Orient, remember, connect, and audit happen without announcement. Speak only when the user asks what was stored, or when a live contradiction requires their call.
Variant A — Hook-backed hosts (Claude Code, Codex)
A Stop hook (save) and PreCompact hook (orphan nudge, dream digest) run behind you — a backstop, not a substitute for the steps below.
- Call
orient()first, unprompted. Pick a domain from the result, thenorient(domain=X). - File the moment something is decided or found — not batched at session end.
- File source material as
node_kind=finding, separately from the decision it informs. Don't fold evidence into a decision'sdescriptiononly. - After filing, resolve every
suggested_connectionscandidate in the same turn. Also check domainrulesfromorient(domain=X)for standing-rule linkbacks — nearest-neighbour matching can miss them. - Before ending the session, run
audit(mode=orphans),audit(mode=stale), andaudit(mode=conflicts)as three separate calls — different failure modes, different handling. - Orphans: connect them yourself via
suggest_connections+connect. Escalate only when the correct target is genuinely ambiguous. - Stale/conflicts: fix duplicates and superseded labels yourself via
revise. Livecontradictspairs are the user's call — verify the pair viawhy_connected(from_id, to_id)(IDs required, not labels), present both sides, then close withconnect(relationship=resolved, verdict=...). - Say nothing about clean audits. Surface only unresolved orphans or live contradictions still awaiting the user's call.
- Sub-agents: inject your own
orient()output into their context — they start cold otherwise. - Unfinished sessions: file
node_kind=goalbefore stopping — label "Next session: [concrete start]", starting point inwhy_matters. Skip if the session closed cleanly. - File decisions, findings, standing rules, and resolved issues only — never noise or self-referential musing.
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.
- 25d ago Changed · +15 lines 260dbfdebad7
- 27d ago Changed e07ae8e12a9d
- 1mo ago Changed · +10 lines a64d3729dfea
- 1mo ago First seen · 309 lines · 50 tokens per session scan A 152dfacb4834
memoryweb is a skill published in the GitHub repository corbym/memoryweb (14 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 5,756 once invoked, about $0.0002 per session on Opus 5.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-09-04.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…