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 activity-monitorgit 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/activity-monitor)<a href="https://agentmods.dev/skills/zylos-ai/zylos-core/activity-monitor"><img src="https://agentmods.dev/badge/skills/zylos-ai/zylos-core/activity-monitor/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/activity-monitor"><img src="https://agentmods.dev/badge/skills/zylos-ai/zylos-core/activity-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 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 Excessive Agency · line 197 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 199 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 207 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 214 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 217 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 220 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 208 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 213 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00036 | $0.02626 |
| Opus 5 | $0.00018 | $0.01313 |
| Sonnet 5 | $0.00007 | $0.00525 |
| Haiku 4.5 | $0.00004 | $0.00263 |
Grade A, and why
activity-monitor 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 13d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activity Monitor Skill
PM2 guardian service that monitors the active runtime agent's (Claude or Codex) activity state and ensures it's always running.
When to Use
This is a PM2 service (not directly invoked by Claude). It runs continuously in the background.
What It Does
- Activity Monitoring: Tracks the agent's busy/idle state every second
- Status File: Writes
~/zylos/activity-monitor/agent-status.jsonwith current state (busy/idle, idle_seconds, health) - Guardian Mode: Automatically restarts the agent if it stops or crashes
- Maintenance Awareness: Waits for restart/upgrade scripts to complete before starting the agent
- Heartbeat Liveness Detection: Periodically sends heartbeat probes via the C4 control queue to verify the agent is responsive, triggering recovery when probes fail
- Health Check: Periodically enqueues system health checks (PM2, disk, memory) via the C4 control queue
- Daily Upgrade: Enqueues a Claude Code upgrade via the C4 control queue at 5:00 AM local time daily (disabled by default; enable with
zylos config set daily_upgrade_enabled true) - Context Monitoring: Receives context usage data after every turn; triggers early memory sync and new-session handoff at thresholds read from
config.json(new_session_thresholdfor Claude,codex_new_session_thresholdfor Codex), each with a built-in runtime fallback if the key is unset
Status File Format
{
"state": "idle",
"last_activity": 1738675200,
"last_check": 1738675210,
"last_check_human": "2026-02-04 20:30:10",
"idle_seconds": 5,
"inactive_seconds": 10,
"source": "conv_file",
"health": "ok"
}
state: "busy" | "idle" | "stopped" | "offline"idle_seconds: Time since entering idle state (0 when busy)source: "conv_file" (reliable) | "tmux_activity" (fallback)health: "ok" | "recovering" | "down" — liveness health from the heartbeat engine
PM2 Management
# Start
pm2 start ~/zylos/.claude/skills/activity-monitor/scripts/activity-monitor.js --name activity-monitor
# Restart
pm2 restart activity-monitor
# View logs
pm2 logs activity-monitor
# Check status
pm2 list
What ships with it
60 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.
- package-lock.json 578 B
- package.json 146 B
- scripts/__tests__/claude-pid.test.js 1.7 KB runs code
- scripts/__tests__/emit-custom-inject.test.js 3.1 KB runs code
- scripts/__tests__/guardian.test.js 5.5 KB runs code
- scripts/__tests__/health-engine.test.js 49 KB runs code
- scripts/__tests__/hook-activity.test.js 7.5 KB runs code
- scripts/__tests__/hook-auth-prompt.test.js 6.3 KB runs code
- scripts/__tests__/memory-sync-gate.test.js 4.0 KB runs code
- scripts/__tests__/memory-sync-integration.test.js 9.5 KB runs code
- scripts/__tests__/message-router.test.js 5.7 KB runs code
- scripts/__tests__/monitor-orchestrator.test.js 43 KB runs code
- scripts/__tests__/session-foreground.test.js 1.7 KB runs code
- scripts/__tests__/session-start-orchestrator.test.js 18 KB runs code
- scripts/__tests__/shard-mode.test.js 18 KB runs code
- scripts/__tests__/shard-sequencer.test.js 9.3 KB runs code
- scripts/__tests__/status-writer.test.js 2.7 KB runs code
- scripts/__tests__/task-scheduler.test.js 4.2 KB runs code
- scripts/__tests__/tmux-input-state.test.js 4.1 KB runs code
- scripts/__tests__/tool-event-stream.test.js 3.8 KB runs code
- scripts/__tests__/tool-lifecycle.test.js 19 KB runs code
- scripts/__tests__/tool-rules.test.js 4.0 KB runs code
- scripts/__tests__/tool-watchdog.test.js 6.2 KB runs code
- scripts/__tests__/usage-check-engine.test.js 1.7 KB runs code
- scripts/__tests__/usage-check-init.test.js 1.1 KB runs code
- scripts/__tests__/usage-codex-rollout-reader.test.js 2.2 KB runs code
- scripts/__tests__/usage-monitor-file-reader.test.js 3.1 KB runs code
- scripts/__tests__/usage-monitor.test.js 4.3 KB runs code
- scripts/activity-monitor.js 43 B runs code
- scripts/adapters/runtime-components.js 5.5 KB runs code
- scripts/claude-pid.js 1.4 KB runs code
- scripts/context-monitor.js 10 KB runs code
- scripts/emit-custom-inject.js 2.2 KB runs code
- scripts/guardian.js 6.8 KB runs code
- scripts/health-engine.js 28 KB runs code
- scripts/hook-activity.js 4.3 KB runs code
- scripts/hook-auth-prompt.js 2.5 KB runs code
- scripts/memory-sync-gate.js 2.6 KB runs code
- scripts/message-router.js 8.0 KB runs code
- scripts/monitor-orchestrator.js 17 KB runs code
- scripts/monitor.js 40 KB runs code
- scripts/proc-sampler.js 8.5 KB runs code
- scripts/session-foreground.js 1.6 KB runs code
- scripts/session-start-orchestrator.js 17 KB runs code
- scripts/session-start-prompt.js 5.2 KB runs code
- scripts/shard-registry.js 12 KB runs code
- scripts/shard-sequencer.js 7.2 KB runs code
- scripts/status-writer.js 1.7 KB runs code
- scripts/task-scheduler.js 2.2 KB runs code
- scripts/tasks/activity-monitor-tasks.js 2.9 KB runs code
- scripts/tool-event-stream.js 5.7 KB runs code
- scripts/tool-lifecycle.js 14 KB runs code
- scripts/tool-pipeline.js 17 KB runs code
- scripts/tool-rules.js 3.1 KB runs code
- scripts/tool-watchdog.js 4.4 KB runs code
- scripts/upgrade-check.js 5.3 KB runs code
- scripts/usage-check-engine.js 984 B runs code
- scripts/usage-check-init.js 436 B runs code
- scripts/usage-codex-rollout-reader.js 4.0 KB runs code
- scripts/usage-monitor-file-reader.js 4.5 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.
- 13d ago First seen · 227 lines · 36 tokens per session scan A a931d5610668
activity-monitor is a skill published in the GitHub repository zylos-ai/zylos-core (1,151 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 2,626 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
error-recovery-skill
Handle errors gracefully with retry strategies and fallback patterns.
multi-tool-orchestration-skill
Coordinate multiple tools together for complex multi-step tasks.
tikhub-skill
Scrape TikTok, Douyin, Instagram, YouTube, Twitter/X, Xiaohongshu, Bilibili, Kuaishou, Weibo, Reddit, Threads, LinkedIn and more through the TikHub pay-per-request API - discover endpoints, call them by id, parse any share URL, and check account balance.
proxy-config-skill
Configure residential proxy providers and make proxied HTTP requests with geo-targeting.
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…
agentic-loop-skill
Autonomous decision loop with reflection and iteration.