Zylos is open-source infrastructure that gives an AI agent persistent memory, scheduled activity, communication channels, and the ability to maintain and extend itself. Individuals and teams use it with Claude Code or Codex through Telegram, Lark, or a web console. Its catalogue add-ons define settings, instructions, and skills for operating the agent.
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 zylos-ai/zylos-core --skill zylos-memorygit clone --depth 1 https://github.com/zylos-ai/zylos-coreWrote 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/zylos-ai/zylos-core/zylos-memory)<a href="https://agentmods.dev/skills/zylos-ai/zylos-core/zylos-memory"><img src="https://agentmods.dev/badge/skills/zylos-ai/zylos-core/zylos-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/zylos-ai/zylos-core/zylos-memory"><img src="https://agentmods.dev/badge/skills/zylos-ai/zylos-core/zylos-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 63 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Output Handling · line 180 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00068 | $0.02405 |
| Opus 5 | $0.00034 | $0.01203 |
| Sonnet 5 | $0.00014 | $0.00481 |
| Haiku 4.5 | $0.00007 | $0.00241 |
Grade A, and why
zylos-memory 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 11d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory System
Maintains persistent memory across sessions via tiered markdown files.
This skill must be run via a runtime-appropriate background subagent mechanism. For Claude, use the Task tool (subagent_type: general-purpose, model: sonnet, run_in_background: true). For Codex, prefer the session's native subagent tools spawn_agent/wait_agent (host session tools — they do not appear in codex --help) with a Codex-supported model; do not hardcode sonnet.
Architecture
~/zylos/memory/
├── identity.md # Bot soul + digital assets (always loaded)
├── state.md # Active working state (always loaded)
├── references.md # Pointers to config files (always loaded)
├── users/
│ └── <id>/profile.md # Per-user preferences
├── reference/
│ ├── decisions.md # Key decisions with rationale
│ ├── projects.md # Active/planned projects
│ ├── preferences.md # Shared team preferences
│ └── ideas.md # Uncommitted plans and ideas
├── sessions/
│ ├── current.md # Today's session log
│ └── YYYY-MM-DD.md # Past session logs
└── archive/ # Cold storage
Memory Sync
Priority
Memory Sync is the highest-priority internal maintenance task. When triggered, run it before handling queued user messages.
Memory Sync is maintenance-only. A sync subagent must not reply through C4, process user-facing tasks, modify business/project repositories, install or upgrade components, restart services, or apply runtime changes outside the sync flow below.
Trigger Paths
- Session init: if C4 unsummarized count is over threshold, launch memory sync.
- Scheduled context check: if context usage is high, launch memory sync.
Both launch a background subagent using the current runtime's supported subagent mechanism with this file's Sync Flow as the prompt.
Codex Background Execution
In Codex, use the session's native subagent tools: spawn_agent to
launch the sync subagent and wait_agent to collect its result. These are
host session tools — they do not appear in codex --help. For a single
long-running command, an async exec session (exec_command +
write_stdin) also works. Bare nohup ... & does NOT survive the
tool-call boundary and must never be used for sync. Never use PM2 for
sync — do not create PM2 services, run pm2 start ... codex exec ..., or
fork an extra codex exec sidecar: one-shot sync processes leave stopped
services piling up in the PM2 list. If the session exposes no native
background-agent capability, run the sync inline as a last resort and note
that in the handoff/status.
What ships with it
29 files 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.
- examples/decisions.md 768 B
- examples/ideas.md 738 B
- examples/identity.md 1.6 KB
- examples/preferences.md 370 B
- examples/projects.md 596 B
- examples/references.md 576 B
- examples/session-log.md 485 B
- examples/state.md 575 B
- examples/user-profile.md 608 B
- package-lock.json 652 B
- package.json 93 B
- references/decisions-format.md 1.2 KB
- references/ideas-format.md 1.3 KB
- references/identity-format.md 1.3 KB
- references/preferences-format.md 1002 B
- references/projects-format.md 1.2 KB
- references/references-file-format.md 2.3 KB
- references/session-log-format.md 1.1 KB
- references/state-format.md 2.4 KB
- references/user-profile-format.md 1.1 KB
- scripts/consolidate.js 3.9 KB runs code
- scripts/daily-commit.js 2.2 KB runs code
- scripts/memory-status.js 2.2 KB runs code
- scripts/rotate-session.js 2.2 KB runs code
- scripts/session-start-inject.js 2.5 KB runs code
- scripts/shared.js 3.4 KB runs code
- scripts/tests/test-rotate-session.js 5.7 KB runs code
- scripts/tests/test-shared.js 4.8 KB runs code
- scripts/tests/test-utils.js 4.2 KB runs code
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.
- 11d ago First seen · 210 lines · 68 tokens per session scan A e164ddf87903
zylos-memory is a skill published in the GitHub repository zylos-ai/zylos-core (1,151 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 2,405 once invoked, about $0.0003 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
install-openviking-memory
Install and configure the OpenViking long-term memory plugin for OpenClaw via natural conversation. Once installed, the plugin automatically captures facts from chats and recalls relevant context before each reply (auto-capture + auto-recall, cross-session). Covers prerequisites, install through OpenClaw's plugin…
compaction-skill
Manage memory compaction by summarizing conversation history when approaching token limits.
openviking-context-database
Use OpenViking from OpenClaw through @openviking/openclaw-plugin: long-term memory, session archives, resource and Agent Skill import, semantic recall, recall trace debugging, and externalized tool-result recovery. Prefer this skill when the user wants to use, query, debug, or operate OpenViking context from an…
memory-skill
Manage conversation memory. Use when user asks to remember something, recall information, view/edit conversation history, or manage short/long-term memory.
ov-experience-memory
Retrieve and apply OpenViking Experience memories through the Agent runtime's generic OpenViking search and read tools. Use before or during executable, multi-step, or tool-based work such as coding, file or data changes, configuration, deployment, workflow execution, and failure recovery when prior operational…
openviking-memory
Recall and persist long-term memory through the OpenViking MCP tools. Use at the start of any substantive task (coding, configuration, debugging, multi-step or tool-based work) to retrieve relevant prior knowledge with find/search/read, and during or after work to persist durable facts, preferences, decisions, and…