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/openclaw/clawdinators/lurknpx skills add openclaw/clawdinators --skill lurkgit clone --depth 1 https://github.com/openclaw/clawdinatorsWrote 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/openclaw/clawdinators/lurk)<a href="https://agentmods.dev/skills/openclaw/clawdinators/lurk"><img src="https://agentmods.dev/badge/skills/openclaw/clawdinators/lurk.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00363 |
| Opus 5 | $0.00010 | $0.00181 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
lurk 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 4d 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.
What it actually says
Lurk Skill
Monitor Discord lurk channels and persist notable activity to shared memory.
When to Use
- Hourly heartbeat (step 3)
- Manual trigger to capture current channel state
How to Run
Use discord.readMessages to read recent messages from the LURK channels listed in AGENTS.md.
- Do not read or write to any channel that is not explicitly listed there.
- These channels are read-only (sendPolicy denies replies).
What to Capture
Persist these:
- Support issues / bug reports
- Questions that indicate user confusion
- Feature requests with discussion
- Anything referencing GitHub issues/PRs
- Repeated topics (multiple users, same issue)
- Announcements or important updates
Skip these:
- Casual chat / banter
- Single-word reactions
- Bot spam
- Already-resolved questions
Output
Append to /memory/discord/YYYY-MM-DD.md using memory-edit (exclusive lock).
## HH:MM #channel-name
- [brief summary of notable item]
- Links to #NNN if references GitHub issue
- @username if relevant
## HH:MM #channel-name
- [another item]
Constraints
- Be selective. Only notable items.
- Include timestamp and channel name.
- Keep each entry to 1-2 lines.
- Cross-reference GitHub issues when mentioned.
- Never write to
/memoryusing raw redirects (>,>>); always usememory-edit. - If nothing notable: don't write anything, reply
NO_NOTABLE_ACTIVITY.
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.
- 4d ago First seen · 60 lines · 21 tokens per session scan A a237a56eccb3
lurk is a skill published in the GitHub repository openclaw/clawdinators (158 stars, last pushed 24d ago), licensed MIT. It adds 21 tokens to every session and 363 once invoked, about $0.0001 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…